Why Vim?
terminally-incoherent.com
terminally-incoherent.com
a) Yes, there are quite a few articles about vim that show up on HN's front page.
b) I am a long time -- 20 years now? Really? Gah! -- vim user, and some of the articles have shown me things that even I didn't know.
Insofar as emacs is concerned, I'm not sure why you are mentioning it. It is a good, respectable editor.
Start with `i` for insert mode and `<ESC>` to return to normal mode. and `:x` to save and quit.
From there, when you want to know what a command does, go to normal mode and type `:help command` Do this once per day. Maybe twice if you feel adventurous. Use `:helpgrep` if you need to find something specific and don't know where to begin.
You will feel like you've been missing out.
Keep in mind that any community or group will have a certain amount of echo-chamber quality to it, if it is growing or churning (which usually happens). The new folks need to see this stuff to understand community norms, and this is a pretty natural way for transmission of that. I work at a university, and I used to feel the same way, about how every fall we would have to go over basics yet again, but then realized that this phenomenon is how we make new grad students into regular grad students. (and I'm pretty sure the getting sick of it step is a requirement for the Ph.D.)
How did that happen? The HN community decided what they liked and continued to reinforce it with articles, blog posts, tutorials. And if the next generation of HNers are to have a similar experience, I don't think that evangelism of such things is a bad thing. Sure, it's boring for you, but we're getting new people here every day.
Want to sell them emacs instead? You can. These choices aren't set in stone, and I'd argue that HN is more or less pragmatic. If something becomes inconvenient to use, cue the posts about alternatives.
(Edit: I enjoy vim. I prefer it to Emacs. I have sometimes found interesting things in these articles. I just think there are too many, and too much zealotry in the community)
As a result, I've looked at plenty of Vim evangelist links on HN looking for inspiration in learning more about productivity with the editor, and honestly?
This is one of the first that has given me some real insight, some workable examples, and something to go on.
It does have a cheerleader tone to it, definitely, but really? I wish more "advocacy/evangelism" posts on HN had this flavor (and substance) to them.
You are constantly challenging yourself to move your hands and fingers in the most efficient way possible. It is incredibly frustrating up front but then you occasionally find yourself elevated and doing something that you had previously thought impossible.
Single key commands strung together make a melody. Editing a document is like playing a song.
Great vim practitioners can elegantly keep tempo and flow with advanced technique and focus.
"If you are using Emacs, keep using it.
Hell, if you are using Java you should probably keep using Eclipse. Similarly you probably shouldn’t ditch Visual Studio and hack your C# code in vim. Emacs and IDE’s are useful – they have tools that will make your life easier. The IDE’s don’t have vim’s raw text manipulation power, but they make up for it by having great integrated debuggers, GUI building tools and etc. But if you are hacking in Perl, Python, PHP, Ruby or something like that, vim is usually a good choice.
Is it the best editor in the world? I don’t know. I guess it depends what you are doing. The bottom line is that you should choose a tool that fits the particular problem you are trying to solve. Not all problems are nails. If you try to apply a hammer to a philipsh-head you are probably gonna screw things up somewhere down the line. But vim is a great editor and you should definitely give it a chance."
1. Because it's installed everywhere.
2. There is no 2.
vi is installed everywhere.
I used to log on Windows servers on a daily basis that had only Notepad.