Reasons To Give The Vim Text Editor A Chance
makeuseof.com
Reasons To Give The Vim Text Editor A Chance
1–10 of 68 posts
Re: Reasons To Give The Vim Text Editor A Chance
#2My reasons for being a vim user a lot more practical than those I see on these "top 10 reasons for trying X":
- In the long run, it's faster to learn and use an "efficiency" editor, so I need to learn one of vim, emacs, notepad++, etc. The differences between these are probably negligible for a proficient user.
- Of these, only vim will be installed (or vi, which has a big enough overlap that it won't matter to me) on every system I'm going to need to use.
These are, incidentally, the same reasons I use QWERTY instead of Dvorak.
Re: Reasons To Give The Vim Text Editor A Chance
#3Coincidentally, all the points equally apply to Emacs. Well, except the last one, I guess.
Re: Reasons To Give The Vim Text Editor A Chance
#4When they started pushing Unix on us in 2nd year CS, I hated VIM with a burning passion. After a little while of using it though, I can say my typing efficiency is far, far, higher than it was before, and I can "flow" better since I don't have to interrupt my stream-of-consciousness with a mouse movement. I wouldn't use anything else nowadays.
Re: Reasons To Give The Vim Text Editor A Chance
#5I love vim, I use it daily, but always for quick text editing. For real coding I need an IDE (netbeans). I never understood how people can code without debugging, profiling, code exploring. I'll probably get voted down, but, what Vim saves me, I wasted it on debugging. So I don't see any advantage using it as my primary editor.
Re: Reasons To Give The Vim Text Editor A Chance
#6I chose it because I am under the impression that it is more ergonomic than Emacs and mainstream text editing environments. I learnt the basics of Emacs before I learnt vi/m.
Re: Reasons To Give The Vim Text Editor A Chance
#7I love vim, I use it daily, but always for quick text editing. For real coding I need an IDE (netbeans). I never understood how people can code without debugging, profiling, code exploring. I'll probably get voted down, but, what Vim saves me, I wasted it on debugging. So I don't see any advantage using it as my primary editor.
Most people that use vim also don't use graphical debuggers. I use the "print" statement.
Re: Reasons To Give The Vim Text Editor A Chance
#8I love vim, I use it daily, but always for quick text editing. For real coding I need an IDE (netbeans). I never understood how people can code without debugging, profiling, code exploring. I'll probably get voted down, but, what Vim saves me, I wasted it on debugging. So I don't see any advantage using it as my primary editor.
I never understood how people can code without debugging, profiling, code exploring.
I'm sure many vim users wonder the same thing. They may also wonder how people can develop using tools that are coupled to each other rather than choosing the various development tools as they see fit.
In any event it's not either/or. The times I've needed Netbeans, for example, I use vim for actual code editing and the IDE for assorted handy click-here-to-run things.
Re: Reasons To Give The Vim Text Editor A Chance
#9Coincidentally, all the points equally apply to Emacs. Well, except the last one, I guess.
Exactly. Emacs doesn't need an elaborate case for its defense; non-modal is more natural/easier-to-learn/BETTER (control-this, control-that) than modal. Not merely my 2 cents -- it's the TRUTH!
Re: Reasons To Give The Vim Text Editor A Chance
#10I love vim, I use it daily, but always for quick text editing. For real coding I need an IDE (netbeans). I never understood how people can code without debugging, profiling, code exploring. I'll probably get voted down, but, what Vim saves me, I wasted it on debugging. So I don't see any advantage using it as my primary editor.
I never understood how people can code without debugging, profiling, code exploring. I'm sure many vim users wonder the same thing. They may also wonder how people can develop using tools that are coupled to each other rather than choosing the various development tools as they see fit. In any event it's not either/or. The times I've needed Netbeans, for example, I use vim for actual code editing and the IDE for assor…
Theres also Eclim for Eclipse which will let you have one of a running modes: Headless eclipse, VIM embedded in the editor, or you can just open it externally.