Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "IDE/Criticism"

< IDE
Line 26: Line 26:
 
**Java completion in IntelliJ matches context.  
 
**Java completion in IntelliJ matches context.  
 
** <strike>Java completion in IntelliJ understands camel-case <code>obj.mM</code> matches <code>obj.myMethod</code>) </strike> works in JDT editor
 
** <strike>Java completion in IntelliJ understands camel-case <code>obj.mM</code> matches <code>obj.myMethod</code>) </strike> works in JDT editor
 +
* Why we dropped Eclipse for IntelliJ? http://www.javacodegeeks.com/2013/09/why-we-dropped-eclipse-in-favour-of-intellij.html

Revision as of 14:59, 19 September 2013

This page aims at listing criticism that is often heard from end-users about Eclipse when comparing IDEs. This can become a list of top priority issues from an end-user POV.

For a better use, this page should contain no judgment from Eclipse contributors. People can discuss on related Bugzilla entries.

Back to the top