Hacker News new | ask | show | jobs
by EuAndreh 1120 days ago
Any sufficiently complicated Vim configuration contains an ad hoc, informally-specified, bug-ridden, slow implementation of half of Emacs.
3 comments

And its half doesn’t include the repetitive stress injuries ;)
> slow

There's quite a good chance that even the most complicated Neovim setup is faster than Emacs. Emacs lisp is notoriously slow, while Neovim uses LuaJIT, which is _very_ fast.

Emacs now has an optimizing native code emitting compiler for elisp. It's definitely not slow, but not as fast a luajit.

Not sure why performance matters in this case anyways though.

How do Neovim and Emacs startup times compare when using Emacs 28’s native compilation of elisp?

Obviously hard to compare because they don’t run the same packages but would still be interesting to see ballpark figures of setups with roughly equivalent functionality.

Are these startup times even significant enough to actually be noticeable anyway?
If people are bothered by Emacs startup times they usually just use Emacs Daemon. I let systemd start it for me at boop, for example.
Not favourably to Emacs.
Emacs Lisp had native-comp now.
A few years ago I would have hated you for this comment but after switching to Emacs, this comment is actually spot on.
I don't like Emacs and still thought it was funny :)