我是Emacs的粉丝，但我鼓励其他开发人员学习VI，因为:

你可以使用VI编辑emacs的makefile文件。 VI包含ed命令，每个UNIX用户都应该知道ed和sed。

我注意到一些关于VIM启动速度比emacs快的评论。如果您真的关心这个问题，请在服务器模式下运行emacs，并将“emacs”别名为“emacsclient”。客户端速度非常快，因为它所做的一切都是轻拍服务器的肩膀，告诉它你想编辑哪个文件。在MacOSX上，emacsclient只有33K，而emacs是287M。

我不确定这些在现代硬件上是否有必要。在我的MacBook Pro (2013 Retina)上，当我从shell运行emacs时，它几乎是立即加载的。我丝毫没有察觉到停顿。当我运行Emacs时。app (GUI版本)可能需要3秒。

我听到的大多数关于emacs的抱怨似乎都来自那些对emacs不了解的人。我从1982年就开始使用vi和emacs了，我清楚地记得，在我早期的UNIX机器中，emacs加载速度比vi慢得多，并且占用了大部分物理内存，但现在已经不再是这样了，至少15-20年都没有了。

我承认的一个抱怨是“emacs小指”。在我年轻的时候，这从来没有困扰过我。现在我已经58岁了，我的小手指确实因为反复使用Control键进行emacs和弦而有点酸痛。在MacBook Pro的键盘上尤其如此，“控制”键向右移动了一个位置，为“fn”键腾出空间。当Control是左下角的键时，它几乎没有那么烦人。

Seems an answer has been selected already, but the big difference to me has always been the modal vs. non-modal. Vim is modal, which means that it makes optimizations based on a specific set of usage modes. At least that's how I've always looked at it. This makes using Vim a different experience because instead of having a work area that you type code in, you really are telling an environment to act on the text. This is why people say things like with Vim you really are learning a language. The :wq and :s/foo/bar is all part of a shell like environment that edits and reads text.

Emacs on the other hand is much closer to most editors/word processors/etc. you see today. You have a workspace that has a highly programmable interface. That is why you see things like email, irc, shells, etc. As a programmer it is easy to think in terms of saying "take the line number I'm on and do something with the information". The desire to leave the editor becomes less because instead of having to quit, open some other app/language and do things on some text, you have Emacs where you can do these things within the scope of your editor.

这两种观点并不一定是对立的，只是它们揭示了两个不同的焦点。就我个人而言，我使用Emacs，但我见过非常了解Vim的人，他们可以诚实地说，选择哪种并不重要。我首先尝试了Vim，但Emacs最终支持了我。的确，无论您选择什么，您都应该至少在一定程度上精通Vim，因为它总是可用的。

对我来说，emacs的优点是，

tramp模式允许您通过ssh编辑远程文件。就像本地文件一样。 Tramp-mode + dired =全功能SFTP客户端 支持您需要的所有语言。 内置的终端模拟器(术语模式)，所以我可以继续编码，而无需在应用程序之间切换。 可扩展性任何你不喜欢的东西都可以用lisp来改变。

Vim was always faster to start up than Emacs. I'm saying that on any machine, out-of-the-box installs of Vim will start up faster than out-of-the-box installs of Emacs. And I tend to think that after a moderate amount of customisation of either one, Vim will still start up faster than Emacs. After that, the other practical difference was Emacs' modes. They make your life tremendously easier when editing XML, C/C++/Java/whatever, LaTeX, and most popular languages you can think of. They make you want to keep the editor open for long sessions and work.

总而言之，我会说Vim让您使用它来完成简短、快速的编辑任务;而Emacs则鼓励您投入长时间的会话。

Emacs具有Viper模式，因此在某种意义上，它提供了一个超特性集(除了那些在使用Viper和Vimpulse的Emacs中缺少哪些Vim特性?)

vi(和VIM IIRC)的重量较轻(它可以就地编辑文件)，但提供的功能较少(子进程通信、扩展语言)。

我想引用《UNIX编程的艺术》一书中的一段话:

Many people who regularly use both vi and Emacs tend to use them for different things, and find it valuable to know both. In general, vi is best for small jobs – quick replies to mail, simple tweaks to system configuration, and the like. It is especially useful when you’re using a new system (or a remote one over a network) and don’t have your Emacs customization files handy. Emacs comes into its own for extended editing sessions in which you have to handle complex tasks, modify multiple files, and use results from other programs during the session. For programmers using X on their console (which is typical on modern Unixes), it’s normal to start up Emacs shortly after login time in a large window and leave it running forever, possibly visiting dozens of files and even running programs in multiple Emacs subwindows.

我在这里真正想强调的是:“许多人发现两者都知道是有价值的。