There's a lot of talk about diversity at Eclipse and it's generally seen as a very good thing. Of course there are exceptions to every rule as Scott Lewis hinted in his blog. Below is a graphic illustration of diversity gone bad. The poor frog has no way to get that misguided toad off his back. Clearly no good can come of this!
I find myself still a bit frustrated with the download page discussions in 205205 . I'll definitely grant that I'm not the best person to judge on what's a good community download page. My experience at IBM with product usability studies taught me that those in the thick of things typically don't have the same perceptions as would a typical user, so it's crucial to consider the users directly. There's a bit of that going on in the bugzilla, but also a lot of experts with expert opinions that may well differ from those of the impacted users; of course I include myself in this comment.
You might consider asking yourself the impression you'd get from the download page as a first time visitor. Could you tell what release you would be getting? If you look way down, you'd see a hint because of the Eclipse Classic 3.3.2 label, but a more prominent mention that 3.3.2 applies for the downloads as a whole would seem to be a good thing. You might even wonder if Eclipse Classic is like Coke Classic? I.e., the way it was before it was ruined by changes? But you'd be digressing badly. Back on track, you might wonder where you could get the latest bleeding edge stuff. Of course there is a "Ganymede M6 Packages" link, but likely you'd think, what the heck is Ganymede and what's so special about M6? According to a comment in the bugzilla, it's hard to find Ganymede with Google even if you already know the appropriate search term.
I definitely don't have all the right answers, but I do get a sense when things don't feel quite right. So while there is a diverse set of opinions on this, it really doesn't seem to have made the page the best I think it could be. Of course that's just my opinion. I would like to think that the big download button on the home page could be used to easily find any other download, i.e., the 3.4 download as well as leads to the downloads for various other projects, with the Eclipse project being the linchpin. Well enough griping. Hopefully I've not offended anyone. Goodness knows our community has some annoying blood suckers, such as yesterday's posting about "I Truly hate Open Source Software," so I don't want to be one of them. Check out the risks some little bloodsuckers are willing to take:
On a more positive theme, the notorious bug 109137---an EMF contributor's words, not my own---has been making excellent progress. The various god-like developers involved in making JDT and PDE great have slaved behind the scenes to produce working results. I'll need to update the instructions for boostrapping EMF from CVS to describe how to exploit this great new support. The approach I'll use going forward is to extract EMF directly into the dropins folder using "eclipse.exe -data dropins" to launch. Once that's all extracted and built, I can launch a runtime workspace and use EMF's wizards to create a new project, generate the source code, and thanks to the new support for external folders on the classpath, the resulting code compiles correctly against the bin folders in the primary workspace.
This is totally awesome, but wait, that's not all! If you right click on the running process for the runtime workspace in the Debug view, you can see the magical incantation that the PDE uses to make the runtime workspace use the development time plugins, i.e., there's a -dev argument that points at a dev.properties file. Now if you record that option, exit your primary Eclipse and restart it with that additional argument, Eclipse will find the development time plugins in the dropins folder and will use the .class files of those plugins to yield a bootstrapped development environment that includes the latest and greatest changes you've just developed without needing to build all the jars! For EMF, this lets me change the generator, quickly restart the environment, and then regenerate my models with those generator changes. I'm now an even happier Eclipse user than before and this is why I truly love open source: people working together to make things better every day.
Metrology in mining and metallurgy
4 years ago