Over a million developers have joined DZone.

Why The Eclipse IDE Is Not At A Crossroads

· Java Zone

Discover how powerful static code analysis and ergonomic design make development not only productive but also an enjoyable experience, brought to you in partnership with JetBrains

After reading Paul Krill's article on InfoWorld about Eclipse IDE At A Crossroads, I have to disagree with some of the main points made. Paring down the Eclipse projects is a totally different thing to dropping features in the IDE. The JDT is one of the most successful and popular parts of Eclipse, as is very apparent from the demographics from EclipseCon 2008.

Of course, some projects that exist right now in the Eclipse ecosystem will change - whether they disappear or merge with others - this is the nature of evolving software. To suggest that the JDT will have to be reduced would be wrong. As discussed in the article, there's people happy with Eclipse and how it is architected. I believe these to be the majority of users.  

Eclipse is based on plugins, so if something isn't required it isn't loaded. Developers have the freedom to add and remove bundles that they require to do their job. There would be no reason to pare down the JDT when this flexibility exists.

Another point raised was the learning curve of Eclipse. While I'll admit that this exists when developing with some of the APIs, as an IDE Eclipse provides first class user assistance. When you start up first you are greeted with a welcome page and links to help documentation and tutorials.

What do you think? Does the JDT need to be pared down, or is it giving you what you need?

Learn more about Kotlin, a new programming language designed to solve problems that software developers face every day brought to you in partnership with JetBrains.


The best of DZone straight to your inbox.

Please provide a valid email address.

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}