Come on, IntelliJ. You are still THE standard in Java development and it's on you to keep that first place. Those "opinins" on Visual Studio Code are ridiculous...
This really makes me want to try out Visual Studio Code for Java.
I remember trying both Netbeans and Eclipse. Both were nice but very slow. Nowadays I sometimes use programs based on eclipse (birt or xmind) and God they make me happy that I'm not doing java dec on Eclipse.
Clunky can mean several things, and I don't think Eclipse changed in any of them since early 00's. If you consider it an specialized IDE (that means you'll download a full one for each kind of development, prepackaged), and disposable (non-upgradable, you'll download the next version and delete the current one), Eclipse is quite ok for many kinds of development (even some you do with Java).
In fact, I think VSCode is one of the best things to ever happen to JetBrains. In particular, Live Share forced them to finally respond with their equivalent product Code With Me (several years too late, but at least it's here).
Without VSC, I don't think JetBrains would be responding nearly as well. It's baffling they consider themselves a full-feature IDE product while having an inferior alpha live share that was rushed through only in response to competition. It's been suggested for years.
I figured Eclipse was the most popular, followed by IntelliJ, followed by NetBeans. Is this mistaken? (I couldn't find a definitive answer with a quick google.)
IntelliJ: 72%
Eclipse: 13%
Netbeans: 3%
Who knows how realistic it is though... I personally enjoyed working with Eclipse. It simply suffers from a reputation problem because people developed monoliths with hundred thousands of lines in a single maven project in it...
I didn't stay long at either place - for some reason both companies were horrible places to work.
I have noticed a lot of new grads come out of College knowing Eclipse (and only Eclipse). Which is probably why it persists - and I still have to deal with it when I have to help junior devs figure out what's wrong with their eclipse config. Occasionally I can get one to convert to IntelliJ - the rest won't try a new IDE and that's a pretty good indicator of what kind of engineer they're going to be :)
I understand the annoyance with not being able to fix one's setup and that's on them.
But it seems very strange to fixate on what other people use as tools... Especially when both propositions are on the same productivity level. It's not like your colleagues are coding java in vim (and even then if productive AF, why does it bother anyone?).
I know one good senior dev who prefers Eclipse. I'm not sure why, but he doesn't seem to have any major issues with it, and he's good, so... ok.
Git's implementation is stronger and more useful for larger projects than Mercurial's, even if the user interface is less logical.
It's not that the software world is driven by hype but that the software world is driven by what the giants do. Often, what Google does isn't right for a small project.
I get it. Most software is boring, doesn't break new ground, and Go is well suited for those kinds of projects.
But I'm becoming an old, cranky developer who wants to work on problems where Go's mediocrity is more hindrance than advantage.
Removing complexity from the language just moves it onto the developer and end-user code, it doesn't eliminate it. Go's mediocrity is a ticking timebomb.
Guess how Go will look like at 25?
Keyword being "supposedly", because in practice, it's quite terrible compared to established solutions like Java and C#.