News for hackers. Stuff that matters.
Re:Your problem with Vim is that you don't grok vi by jff on Monday August 22, 2011 @11:59AM (#2912876)
I've found that using code correction and autocomplete serves rather to break up the flow of putting code down. It's not important that I wrote "mlloc" instead of "malloc", the compiler will catch that later and I can fix it then. The important thing is that I remember how big I wanted to make the memory region, and then what algorithm I was going to apply in the Big Important Loop coming up.

And if you need code completion, your names are too long ;)

Re:Your problem with Vim is that you don't grok vi by kevinkemp on Monday August 22, 2011 @02:04PM (#2913385)
I can appreciate continuancy of mind, but red squiggles shouldn't be a deterrant to that. Rather, it is simply saving you the step of compiling before giving you information. You can just as easily train yourself to not worry about red squiggles until you're finished with the task at hand.

As for variable naming, the better question is:

Why would you willingly choose less descriptive variable names when there are editors that will help you produce more readable code?

Re:Your problem with Vim is that you don't grok vi by stonemetal on Tuesday August 23, 2011 @10:35AM (#2916709)
editors that will help you produce more readable code? The problem is your editor helps you produce more code, readable or not. The goal is to produce a good program, not more code.