Posted by: Administrator
on January 25, 2007 10:45 AM
Well, trying to conclude my ever wondering 'is vim better' in 2 lines sounds just so easy, but really... it is that hard to find out how useful vim is, and it never brought me more productivity than the Windows editors in the past few years.
Certainly, you can map command in Windows editors too, and whatever the plugins that they offer, I don't find them any useful.
Say, foldings... why do you hide your code? You might forget about a variable at certain place and make a new bug thinking it's not used. If your code is too long... just split the files up...
Function name auto completion? If you're a serious programmer, you really do already remember most of the function names that you usually use along with the parameter requirements, but if you do get stuck in that, you should refer the actual language doc.
Display split? Seriously, seeing only 1% of the whole code makes a real sloppy coding and is prone to serious coding problems as you have less code revealed to yourself, I never split screen.
Now, what Windows editors offer, where Vim doesn't are.
Visually pleasing layout, you can definately see what files are open in tabs (now that vim finally caught up). You know if the file is at the last saved state by looking at if the 'Save' button is greyed out or not. You see the encoding method and total line numbers and all (though latter is visible in vim too). And with a explorer extension, you can even have a list of files displayed on your left or right edge to figure out a good strucutre of your project and easy file opening, instead of in vim, you start out with<nobr> <wbr></nobr>:tabnew and blindly typing in folder and file names and keep pressing 'tab' to find out the file name matches and open file, and if you want to open yet another file in yet another folder, you have to dig through again, until you do a 'cd' first, which is completely reluctant to do than simply visually looking through the whole project file structure and clicking through it while maintaining visible information on the parent folders.
So, say what's better about vim again.
Just to troll (with a good reason) a slightly bit to fire up vim lovers =) but why do 95% of vim themes look super ugly? Do you think people would even code good with 'blue' color scheme? It hurts my eyes from the first second.
Learn about Linux
Download Linux
Get Linux help
Re:Why Vim?
Posted by: Administrator on January 25, 2007 10:45 AMCertainly, you can map command in Windows editors too, and whatever the plugins that they offer, I don't find them any useful.
Say, foldings... why do you hide your code? You might forget about a variable at certain place and make a new bug thinking it's not used. If your code is too long... just split the files up...
Function name auto completion? If you're a serious programmer, you really do already remember most of the function names that you usually use along with the parameter requirements, but if you do get stuck in that, you should refer the actual language doc.
Display split? Seriously, seeing only 1% of the whole code makes a real sloppy coding and is prone to serious coding problems as you have less code revealed to yourself, I never split screen.
Now, what Windows editors offer, where Vim doesn't are.
Visually pleasing layout, you can definately see what files are open in tabs (now that vim finally caught up).
You know if the file is at the last saved state by looking at if the 'Save' button is greyed out or not.
You see the encoding method and total line numbers and all (though latter is visible in vim too).
And with a explorer extension, you can even have a list of files displayed on your left or right edge to figure out a good strucutre of your project and easy file opening, instead of in vim, you start out with<nobr> <wbr></nobr>:tabnew and blindly typing in folder and file names and keep pressing 'tab' to find out the file name matches and open file, and if you want to open yet another file in yet another folder, you have to dig through again, until you do a 'cd' first, which is completely reluctant to do than simply visually looking through the whole project file structure and clicking through it while maintaining visible information on the parent folders.
So, say what's better about vim again.
Just to troll (with a good reason) a slightly bit to fire up vim lovers =) but why do 95% of vim themes look super ugly? Do you think people would even code good with 'blue' color scheme? It hurts my eyes from the first second.
#