This is so wrong. vim has eclim, which is a bridge to Eclipse (you can either run Eclipse visually or use Eclipse in server mode) and provides all the Eclipse auto-completion. It just works.
It actually works so well that the "emacs eclim", based on eclim, "Just Works! [TM]" and gives you, right inside Emacs, the Eclipse auto-completion.
Even when stuck in the Java/ORM/Hibernate/SQL/XML hell (at which point I want to kill myself and really question the company's "productivity"), I'd still rather use Emacs + emacs-eclim then Eclipse (or IntelliJ IDEA -- which gives both NetBeans and Eclipse a run for its money btw).
Thing is: adding Eclipse / IntelliJ support to vim / emacs is not that hard. But turning the "text editor" part of Eclipse into Emacs just looks like mission impossible.
IIRC using eclim you can replace the (very lame) text editor of Eclipse with vim. So you get vim running right in the middle of your Eclipse.
It actually works so well that the "emacs eclim", based on eclim, "Just Works! [TM]" and gives you, right inside Emacs, the Eclipse auto-completion.
Even when stuck in the Java/ORM/Hibernate/SQL/XML hell (at which point I want to kill myself and really question the company's "productivity"), I'd still rather use Emacs + emacs-eclim then Eclipse (or IntelliJ IDEA -- which gives both NetBeans and Eclipse a run for its money btw).
Thing is: adding Eclipse / IntelliJ support to vim / emacs is not that hard. But turning the "text editor" part of Eclipse into Emacs just looks like mission impossible.
IIRC using eclim you can replace the (very lame) text editor of Eclipse with vim. So you get vim running right in the middle of your Eclipse.
What's not to love there?