&gt; A GUI editor can do everything a terminal based emulator can; there are lots of things a GUI editor can do that a text editor can&#x27;t.<p>Really? I&#x27;d like to see sublime handle text manipulations with the same efficiency and precision that Vim provides.<p>&gt; What is the advantage of terminal based editors? As far as I can see, ubiquity, which is made less compelling when you need a host of plugins to do the things you mention.<p>What about integration with the shell? It&#x27;s not merely a matter of ubiquity: I don&#x27;t <i>really</i> need a document tree when I have the entire terminal at my disposal a :sh or :wq away.<p>&gt; Terminal editor enthusiasts seem to be under the effects of something like the Blub paradox, where any feature of a GUI editor described to them is dismissed with &quot;why would I ever need that?&quot; while anything in terminal emulator can do is considered essential.<p>This would be an apt description if the majority of &quot;terminal editor enthusiasts&quot; were as inexperienced with GUI editors as their GUI counterparts, but in fact the opposite is true. Most Vim&#x2F;Emacs users tend to have hundreds of hours experience working with GUI editors, but are for some reason convinced that they (the editors) were inferior. Finally, let me give you an irrelevant (but fun) fact: PG, the original proposer of the Blub paradox, uses vi.