3 ms·
I used Eclipse daily for the last year and regularly for five or so before that. I've switched to Netbeans in the past (and back because of concerns at work--ou
by eropple 15y ago
I used Eclipse daily for the last year and regularly for five or so before that. I've switched to Netbeans in the past (and back because of concerns at work--our build process hates Netbeans) and have been using IntelliJ for the last three months. Since switching to IntelliJ, I've never been happier when working in Java (would still prefer Visual Studio to any of this, though).
IMO, anyway, Eclipse's problem is that it doesn't feel like an IDE. It feels like a framework for making IDEs, and Java's sort of bolted in. The user experience is not good, and worse when using non-Java language. A lot of this can be chalked up to Eclipse being a very early example of this sort of IDE framework design, but there are a lot of warts that have just never been fixed.
It's just not a comfortable environment. Honestly it feels like the developers of the Java ecosystem atop Eclipse went "eh, close enough" at one point and it's stayed there for half a decade. It doesn't feel like anyone spent time looking at how users actually write code, but rather went off how they wrote code and extrapolated it to their userbase.