Slashdot Mirror
Eclipse Foundation Celebrates 10 Years
msmoriarty writes with news that the Eclipse foundation is ten years old this week. Although Eclipse was released in 2001, development was controlled by IBM until the creation of the independent Eclipse Foundation in 2004. "According to Eclipse Foundation Director Mike Milinkovich, that's a major reason Eclipse was able to thrive: 'IBM....did an exemplary job of setting Eclipse free ... We became the first open source organization to show that real competitors could collaborate successfully within the community.' He also talks about misconceptions about Eclipse, its current open source success, and what he sees for the future."
Even though I've owned a copy of IntelliJ IDEA for over a year, I still use Eclipse everyday for Java development. Latest version is great and the extensions available for it make it even better.
Reviewing just the first hour of video games.
I always found Eclipse to be very fidgety, and I've only ever been able to get one non-java project debugging properly inside of it. Conversely, netbeans ... well.. it just works. It has full C++11 support these days, and is, in my opinion, much friendlier to pure java development, using ant as its native build tool.
(My money's on this comment being modded down by eclipse fanboys, ah, but what the hell, I'll post it anyways.)
File under 'M' for 'Manic ranting'
I've been using Eclipse on for pretty much 10years now and by and large, the tool has been pretty darn soliod. its a memory pig so get over it. I throw 1.5G at the heap and though it rarely if ever gets close to it, the amout of speed it performs mosdt operations is amazing.
There are warts which I find personally lousy (like Mylyn of the built-in profiler, and much of the built-in text validators), but thankfully most of those can be trivially turned off and tweaked to speed up usage even more. With a few choice plug-ins, you can do a lot of the hard lifting without effort.
I've only had cursory usage of Netbeans/Idea, but Kepler is really a dream to use. Note, almost every first few months of a new release are generally ass, and Juno was entirely ass so be warned. Just because one version of Eclipse may be a flake, don't discount the platform.
Bye!
...and I'm still waiting for it to load!
One of the most awesome things that the Eclipse people did was switch to a foundation built on OSGi after the first version. Eclipse is a showcase that showcase the power of a modular component framework.
Sun really screwed up by failing to adopt OSGi for Java's module system.
When I think of the best technologies available to the average Java developer like myself I rank the JVM first and OSGi second.
With setup boxes now set to become ubiquitous, I want a box that integrates some OSGi-like framework that will enable me to integrate all the devices in my house.
Have you ever looked at the code behind eclipse? It's terrifying!
No, I haven't. But I'll concede that anyone who can write bad code in Java can write much worse code in C++.
From the limited time I've spent in eclipse's code, it seems a case of poorly done decoupling. It's layers upon layers of abstraction that's expected to just kinda sort itself out, which of course it doesn't and things end up in loops until the operation either times out, fails, or something changes that lets it get out of the loop and maybe even finish.
Clicking the cancel button is optimistic at best, especially when it's in one of it's death patterns. It just really seems to do a poor job of operation management in my opinion. When eclipse seems to be "taking forever", chances are it's two operation tasks bouncing back and forth waiting on each other, and not actually slow processing.
That said, I still love eclipse for Java development. Once you learn the do's and don'ts (and which files to delete when eclipse has a melt down), it's pretty usable.
except you can use emacs to do things