That's about right. It's true that my experience with Java is not representative, but I'm still unclear what would happen if I did manage to get Eclipse working correctly. Emacs can organize imports, complete symbols, jump to definitions, and things like that. It can't refactor as intelligently as I imagine Eclipse can, but the one time I've needed to do a really big refactor I just did it manually with a Perl one-liner (I should have written a full script, in retrospect) and cleaned up the handful of mistakes when reviewing the diffs.

(That's generally how I feel about Eclipse. It will spend several hours analyzing your source code so it can do a perfect variable rename. But you can get 99.99% of the way there with "perl -pi -ne 's/int foo/int bar/g'" and fix the two cases it broke in seconds. I'd rather not write that and not do the fixup, but with so much cognitive load to make that automatic, it just isn't worth it. Why does refactoring Java require a complicated GUI application with more settings than the Space Shuttle?)

The one feature I really want is something that detects what problem I'm trying to solve and shows me the documentation for libraries that can help.

But really, I wish someone would write an article like "why I switched from vim to Eclipse", but I only ever see ones where the author does the opposite.