Maybe I just don't fat-finger as much as the typical programmer...but intelligent code completion and typo detection are really not things I value in an editor. <C-N> buffer-based completion is more than sufficient when I need to save some typing.
It also depends upon the language you are using. I don't know if you're using Java or not but one can use all the help possible in catching typos while working in Java just due to the verbosity of the language. Programming in Java without an IDE is like working on rails apps without using any of the scripts and generators, it's doable you just have to write all the boring boilerplate code manually.
Also, using autocomplete to explore APIs is one of the worst programming practices I can think of. The docstring for one method is not nearly enough information to tell you why you should call the particular method of the particular class that autocomplete suggested. In order to be sure you've made a good API use decision, you need to read the documentation and code for the library, and then decide to use it. Anything else is a hackish shortcut that will surely waste more of your time than it saved.
And, if you can't remember the names of methods you know you want to use, maybe it's time to refactor. Or practice remembering. If you want to be bad at programming, Eclipse will make your life slightly easier. If you want to be good at programming, start programming and stop commanding an autocomplete tool.
I primarily use Vim as my IDE, so I'm not saying I prefer Eclipse or other IDEs. But I don't pretend that Vim is perfect and using an IDE is a sign of inability.
Now, I much more highly value consistency. In any given day, I may edit one of a dozen languages or hundreds of config file formats.