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 25: Line 25:
 
**Eclipse doesn't have inner language completion (completion for an XPath expression inside Java code) compared to IntelliJ  
 
**Eclipse doesn't have inner language completion (completion for an XPath expression inside Java code) compared to IntelliJ  
 
**Java completion in IntelliJ matches context.  
 
**Java completion in IntelliJ matches context.  
**Java completion in IntelliJ understands camel-case <code>obj.mM</code> matches <code>obj.myMethod</code>) '''Solution?''' Make complation for <code>obj.xyz</code> actually match <code>obj.x*y*z</code>
+
** <strike>Java completion in IntelliJ understands camel-case <code>obj.mM</code> matches <code>obj.myMethod</code>) </strike> works in JDT editor

Revision as of 08:14, 20 August 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