|
|
|
|
|
by bitwize
3292 days ago
|
|
Yeah, except no. The vi vs. Emacs editor wars are over and Emacs lost. The new struggle is between vim and modern IDEs and IDE-like editors (Atom, Sublime, etc.). There are reasons for this. Vim is retro like beehive hairdos; Emacs is retro like casual workplace sexism. The buffer implementation in Emacs sucks. Once you start opening huge files or running shell tasks that spew a lot of output, Emacs chokes hard and because it's not multithreaded, pegs your CPU and locks up your terminal, in buffer sizes that modern editors handle easily. Also, Elisp is slow, contains warts the Lisp community has long since fixed, and is in general a millstone around everybody's necks. Also, the UI. Just... the UI. Wonder why the best way to get a young developer to use Emacs is to reskin it like vim (evil-mode, Spacemacs)? Editors, even all-in-one kitchen-sink editors, have moved on from Emacs. Just let it go. |
|
I learned vim first and later switched to Emacs because it allows me to integrate all tasks in the same work environment. The defaults are admittedly terrible and it's certainly far from perfect. But I don't see any alternative that works better for the things that I use Emacs for. I am looking forward to eventually be using Guile instead of Elisp, though.
Curious that you mention the UI as a negative(?) --- the Emacs UI is pretty good actually and it's very extensible.