4 ms·

I tried getting into IntelliJ and, though look and feel wise and it is superior to Eclipse in every way, there is just so much lacking that I am used to in Ecli

I tried getting into IntelliJ and, though look and feel wise and it is superior to Eclipse in every way, there is just so much lacking that I am used to in Eclipse. Maybe I am just not used to how IntelliJ does things... I use IntelliJ primarily for Play Framework development. I've installed plugins for almost all other languages (node.js, python, mustache etc) and use IntelliJ for that but for non-Play Java, I tend to go back to Eclipse. Some of that may be the 10 years or so now that I've spent with Eclipse.

arielweisberg 13y ago
I tried IntelliJ and had the same reaction. I did find that IntelliJ had complete parity once properly configured and shortcuts were learned except for two showstoppers. Complilation was not continous and was slow, and in the debugger you can't pause a specific thread you can only pause all threads. I did find that some common operations I do through the GUI require more clicks then when I do them in Eclipse. I didn't find it enough better to switch, but I run on fairly honkin hardware (Ivy Bridge i7, 16 gigabytes of RAM) and I changed the Eclipse default heap size to 2g.
cromwellian 13y ago
In terms of multilanguage editing, refactoring, and just basic Java handling, IntelliJ blows away Eclipse. I've been switching back and forth between the two for years because of internal Google bias towards Eclipse, but I find Eclipse to be very lacking. Just simple stuff like Find Usages or navigating type hierarchies is done far better in IJ.
- cmsimike 13y ago
  What do you find that is different? I've never had a problem with type hierarchies or Find Usages in Java (not counting JSP - JSP support is terrible). For JUST Java, IMO Eclipse wins for me.
  - cromwellian 13y ago
    Well, if there are two inner interfaces called "Callback" like public class Foo { interface Callback {} } public class Bar { interface Callback {} } The last time I asked Eclipse to find all implementors of Bar.Callback, it actually returned ALL instances of any interface called "Callback" as if it is just doing a String search and not actually using type hierarchy information in the search. Eclipse auto-assist often popups up tons of bullshit that is not relevent, like asking to import say, a class called 'Util', Eclipse would often show all kinds of entries from private com.sun.* classes in the JRE/JDK first. It's as irritating and choosing what Country you're form in a Web Form and it has Afghanistan first and United States at the end, even though it should know from locale or Geo-IP how to sort better. Maybe this has been fixed recently, but it has always worked the way it should in IntelliJ. IntelliJ also handles Maven better. And it handles integration between Java and other DSL languages better. IntelliJ's PSI model of code is far richer than JDT.
- deleted 13y ago
  [deleted]

arielweisberg 13y ago

I tried IntelliJ and had the same reaction. I did find that IntelliJ had complete parity once properly configured and shortcuts were learned except for two showstoppers. Complilation was not continous and was slow, and in the debugger you can't pause a specific thread you can only pause all threads. I did find that some common operations I do through the GUI require more clicks then when I do them in Eclipse. I didn't find it enough better to switch, but I run on fairly honkin hardware (Ivy Bridge i7, 16 gigabytes of RAM) and I changed the Eclipse default heap size to 2g.

cromwellian 13y ago

In terms of multilanguage editing, refactoring, and just basic Java handling, IntelliJ blows away Eclipse. I've been switching back and forth between the two for years because of internal Google bias towards Eclipse, but I find Eclipse to be very lacking. Just simple stuff like Find Usages or navigating type hierarchies is done far better in IJ.

cmsimike 13y ago
What do you find that is different? I've never had a problem with type hierarchies or Find Usages in Java (not counting JSP - JSP support is terrible). For JUST Java, IMO Eclipse wins for me.
- cromwellian 13y ago
  Well, if there are two inner interfaces called "Callback" like public class Foo { interface Callback {} } public class Bar { interface Callback {} } The last time I asked Eclipse to find all implementors of Bar.Callback, it actually returned ALL instances of any interface called "Callback" as if it is just doing a String search and not actually using type hierarchy information in the search. Eclipse auto-assist often popups up tons of bullshit that is not relevent, like asking to import say, a class called 'Util', Eclipse would often show all kinds of entries from private com.sun.* classes in the JRE/JDK first. It's as irritating and choosing what Country you're form in a Web Form and it has Afghanistan first and United States at the end, even though it should know from locale or Geo-IP how to sort better. Maybe this has been fixed recently, but it has always worked the way it should in IntelliJ. IntelliJ also handles Maven better. And it handles integration between Java and other DSL languages better. IntelliJ's PSI model of code is far richer than JDT.
deleted 13y ago
[deleted]