abm (14) amp (18) ascape (6) biomed (6) business (22) butterflyzer (9) dharma (12) eclipse (62) emf (7) graphics (10) ip (8) java (35) life (5) osx (13) science (13) web (6) xpand (5)

Monday, May 17, 2010

What makes it "classic"?

OK, this one's short and sweet. But not New Coke sweet, I promise. Does it bug anyone else that the Eclipse download that most people who develop for Eclipse use, and the one that is in fact the second most popular, is referred to as the "Classic" build and appears at the bottom of the downloads page?



Sure, we're all used to it now, but for someone new to the platform, does it really make any sense? Originally I had suggested "Eclipse Core Platform" to replace the Classic package name -- an admittedly somewhat lame name. But Ian has suggested "Eclipse SDK" as an alternative, and I think it's a great idea.

You can check out all of the fascinating pros and cons at bug 273930. And if you like the idea, please vote for the bug..Helios is just around the corner.

1 comments:

  1. I've been using Eclipse for many years, and it was only recently that I found out what the "classic" download was. The Scala plugin for Eclipse recommends using the "classic" version, and I had avoided it, because I assumed it was either older or would not contain all the features I was used to. When I finally investigated, I discovered what it really was. Calling it "classic" makes no sense, and is most likely confusing to those who are not part of the Eclipse inner circle.

    ReplyDelete

Popular Posts

Recent Tweets

    follow me on Twitter