If you are looking for an objective analysis of both the editors, look at their origins and the philosophy behind their respective designs. Think, which one would suit you better and learn it (and learn it and learn it, because it takes time before you being to discover its true utility as against any IDE). An Introduction to Display Editing with Vi was written by Bill Joy and Mark Horton and he explains why he choose modal design and rationale for various key strokes ( it helps me to remember that CTRL-W +W (will switch to next Window and it will same for CTRL W+ CTRL W, just in case you held the CTRL key for a longer duration.

这里有一个Emacs时间轴的链接，并有对Multics Emacs论文的参考。这是一篇关于Emacs的RMS论文，我看到重点在可编程文本编辑器上(甚至早在1981年或更早的时候)。

我没有读过emacs的论文，但是读过Bill Joy的vi论文几次。 两者都是旧的，但你仍然会得到哲学，你可以选择使用当前的工具(vim 7。X还是emacs 25?)

编辑:我忘了说，阅读这两篇论文需要耐心和想象力，因为它会让你在阅读时回到过去。但这是值得的。

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则鼓励您投入长时间的会话。

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，因为它总是可用的。

我想引用《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.

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

对于我来说，选择使用emacs而不是vim的最大区别是emacs内置的gdb支持。Vim的默认发行版中并没有包含这个功能，而且用于集成gdb和Vim的项目几乎不可能使用MacVim

关于这两个编辑器，已经说了很多，但我只想补充我的5便士。这两个编辑器都很棒，你不会选错他们中的任何一个。

我使用vi/vim已经有15年了。我试过几次转换到emacs，但每次都发现vim实际上可以做缺少的事情，而不需要写一个lisp扩展或安装一些东西。

对我来说，编辑器的主要区别是vim让你使用环境/操作系统，而emacs试图封装它或替换它。 例如，您可以在文本中添加日期:r!日期在vim，或日历与:r!ccal1 2014，甚至用十六进制版本的内容替换缓冲区的内容。如。: % !Xxd，编辑十六进制，然后返回:%!XXD -r，以及许多其他用途，如内置grep, sed等。

另一个例子是使用jq和gron。如。将json blob粘贴到编辑器，然后运行转换:

:r!curl -s http://interesting/api/v1/get/stuff
:%!gron | grep 'interesting' | gron -u

OR

:%!jq .path.to.stuff

上面的每个管道命令都可以通过:%!<命令>，其中%表示所有文档，但也可以对选定的行等运行。这里gron输出可以作为jq路径。

您还可以获得EX批量编辑功能，例如。替换某些单词，重新格式化代码，转换dos->unix换行符，一次对100个文件运行宏。这很容易用ex完成。我不确定emacs是否有类似的东西。

换句话说，IMHO vim更接近unix哲学。它通常更简单、更小，但是如果您了解您的操作系统和工具，您可能只需要VIM提供的东西。我从来没有。

此外，vi在任何unix/linux系统上都是事实上的标准，为什么要学习使用两个做同样事情的工具呢?当然，有些系统提供mg或类似的东西，但肯定不是所有的。Unix + Vi <3。

好吧，只要我的5便士。