News for hackers. Stuff that matters.
Re:Your problem with Vim is that you don't grok vi by oinksoft on Monday August 22, 2011 @11:07AM (#2912676)
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.
Re:Your problem with Vim is that you don't grok vi by theshadow on Monday August 22, 2011 @06:22PM (#2914391)
The point of code completion is not just to save typing (although that is desirable benefit), code completion helps you browse around a new library that you're unfamiliar with and read the documentation right in the IDE. I don't know how I would have gotten through the Swing/SWT based assignments in school without have the documentation right there in IDE.

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.

Re:Your problem with Vim is that you don't grok vi by jrockway on Monday August 22, 2011 @06:29PM (#2914413)
As with anything, after you start practicing you stop making beginner mistakes. If you switch to Emacs or Vim today, you are going to typo things that Eclipse would have auto-corrected for you. That's because you've never practiced typing correct code from memory. But use Emacs or Vim exclusively for a month, and you'll see that you are much better at programming than Eclipse is. You'll write code more quickly with fewer errors.

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.

Re:Your problem with Vim is that you don't grok vi by gabyar on Monday August 22, 2011 @06:51PM (#2914494)
Code completion, syntax validation, and built-in API documentation are useful features. To say they're things that only beginners or bad programmers use is absurd. I have much better things to do with my time than memorize the exact name and parameter order of every method in an API.

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.

Re:Your problem with Vim is that you don't grok vi by snprbob86 on Monday August 22, 2011 @02:41PM (#2913537)
This used to be something I greatly valued in IDEA and VS when writing Java and C# respectively.

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.