3 ms·

I don't think IntelliJ has added support for running non-compiling Java code yet, which was a major productivity booster for me. Eclipse's ability to debug and

I don't think IntelliJ has added support for running non-compiling Java code yet, which was a major productivity booster for me. Eclipse's ability to debug and run a single failing unit test were massive as well. IntelliJ was always hit or miss as to whether it would allow you to run a subset. IntelliJ refactorings also were a lot less smart IMO - often trying to refactor unrelated comments and sometimes code that was unrelated but happened to be named the same thing.

drdec 4y ago
> running non-compiling Java code yet I don't mean to sound rude here, but that just sounds like nonsense to me. How are you supposed to run code that won't compile? Does eclipse just generate random bytecodes for the party that doesn't compile? > debug and run a single failing unit test I'm not sure where the issue is for you, but this has always been available since I have used IntelliJ, going back 15 years.
- innocenat 4y ago
  Eclipse normally use its own compiler, JDT Core, which support many features Oracle JDK doesn't. https://www.eclipse.org/jdt/core/ https://www.eclipse.org/jdt/core/ > An incremental Java compiler. Implemented as an Eclipse builder, it is based on technology evolved from VisualAge for Java compiler. In particular, it allows to run and debug code which still contains unresolved errors.