Incremental compilation.
You could make a small change, do a Ctrl-S, and Eclipse would compile the change nearly instantly, where all competing products (that I was aware of, correct me if you know better) needed to fire up a Java compiler and feed it at least all changed source files. For me, this was difference of 2 seconds versus maybe 20-30.
I remember this word from the movie submarine.
It does, and it's much better than javac for IDE use cases. That's one of my biggest pain points with IntelliJ. They've tried to implement some kind of incremental compilation on top of javac, but it doesn't work reliably and often forced 5-minute from-scratch recompiles on the last project I worked on.
Eclipse comes with its own compiler and ONLY requires the JDE to develop Java application, not the JDK.
They also claim that its their compiler that implements the incremental compilation
https://www.eclipse.org/jdt/core/
>JDT Core is the Java infrastructure of the Java IDE. It includes:
>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...
>...The JDT Core infrastructure has no built-in JDK version dependencies, it also does not depend on any particular Java UI and can be run headless.
Not only that, but what does it matter if incremental compilation is "not tied to the compiler" if Eclipse was the only software that utilized it at the time?
Java Hotspot has always been a huge productivity booster.
I think they've retrofitted Mono to run in interpreter mode or something in order to get around those restrictions