Its suggestions stuff is nice, and it works reasonably well. In particular it supports multiple languages much better than Eclipse's motley range of plugins. So I can see why your list of uses makes it the superior option there.

But for primarily Java development, which is where I encounter it and the most vocal love for it, it lacks a couple of key features (or non-obvious configuration to enable them I guess?)

* You can't run code unless the whole project compiles (poor for quick sanity check, test driven development, and refactoring breaking changes).

* You don't get the "problems" view of compilation issues (and optionally analysis output like findbugs) so as often as not I'll try to run a test, building the whole shebang, when the end result will be needing to fix a trivial syntax error. Eclipse tells me that first.

* It's a pain to use when working with multiple (source independent) projects simultaneously. E.g. a library project and the main project. Eclipse lets you open anything you want to in the same window and presents them in the same explorer view.

It also, anecdotally, feels slower than Eclipse, and seems to enjoy popping up focus-stealing windows more often than Eclipse (though I guess I can cuss Gnome just as much for that one).

I don't hate it, but I do miss Eclipse.

Edit: I should add that it supports Gradle rather better than Eclipse does, but since I really dislike Gradle I'm not sure how much of a plus that is!