4 ms·
I couldn't disagree more. I had the hardest time switching over to Vim because there is such a high learning curve, but once it "clicked", I could never back.
by adam_albrecht 16y ago
I couldn't disagree more. I had the hardest time switching over to Vim because there is such a high learning curve, but once it "clicked", I could never back. Sometimes I'll have to do some .Net work in Visual Studio and I feel like I just switched from a Ferrari to a Corolla.
Now, if you're doing work in compiled languages like Java and C#, the code-completion of Visual Studio and Eclipse is very valuable. But besides that, I'd much rather have a simple and fast editor over a bloated IDE with tons of features.
- mbowcock 16y agovi emulation in visual studio - https://github.com/jaredpar/VsVim https://github.com/jaredpar/VsVim
- jodrellblank 16y agoYou don't use Vim 7 completion? http://linuxhelp.blogspot.com/2006/09/visual-walk-through-of-couple-of-new.html http://linuxhelp.blogspot.com/2006/09/visual-walk-through-of...
- dougws 16y agoI'm a dyed-in-the wool emacs user (and have played with vim quite a bit) but there's really no comparison between the "completion" vim and emacs offer and that provided by IDEs like VS and Eclipse. They do quite a bit of static analysis and do context-sensitive completion which is extremely helpful when the standard library for your language has a ridiculously bloated API (like, for instance, Java and .NET).