Hacker News Reader

Comment by grigjd3 | Hacker News Reader

I still hear the old joke sometimes:

Emacs user: You should never turn off emacs.

Vim user: because it takes too long to load emacs.

The irony being the points behind both sides of this joke pretty much have no meaning with the current state of technology.

View on HN

Not really. I'm an Emacs partisan, but my Emacs takes at least 3 seconds to load (often 4 or even a little more), while vim is instant.

It is faster than Google Docs or MS Office, but the lag is noticeable.

Vim is not instant. Moreover, it has annoying TTY handling behaviors; it flushes the TTY when starting.

So if I type

   $ vim file

and start entering editing commands, often I do it so fast that some of the characters get cut off, like the leading colon of an ex command or what have you.

There is no good reason for this. It will not happen with any reasonable command line utility.

I reported this to the Vim mailing list not long ago and was basically brushed off.

I read https://groups.google.com/d/msg/vim_use/XX6SoxHAzhI/vuyIx71G... and it doesn't look like a brush-off to me.

What's missing is the statement that this is how things work when one is relying upon terminals to respond to special control sequences with strings denoting their capabilities. In theory one could save up and re-process the input characters that arrive before the DECDSR response. In practice, people throw them away.

Did you try it on a non-xterm terminal type, as was suggested?

Have you reported it to the Neovim devs? It stands a better chance of being included there (IMHO) and from there it's possible that it trickles up (like the async features in Vim 8).

I love vim but recently started using Emacs with spacemacs and it takes a long time to load. Vim is basically instantaneous and Emacs is like molasses.

(emacs-init-time) "0.2 seconds"

Use autoloads everywhere. Put all per-package configuration in lambdas executed on hooks, or eval-after-load. Lazy-load Helm by mapping M-x to helm-M-x etc. - small ad-hoc edits probably don't even need Helm.

I still use emacs --daemon / emacsclient (aliased to 'e'), but I keep my $EDITOR set to emacs. There's no good reason to have a long wait for startup.

Well I certainly don't dig into the depths of what I can make emacs do (and hence load) but I find it opens seemingly instantly for me unless I am doing something like using the window mode on a VM that mimics a video card.

Run as daemon https://www.emacswiki.org/emacs/EmacsAsDaemon

I should not need to run a background daemon for my text editor to load quickly.

True, but it's pretty reasonable for your nested OS to take a while.

Enjoy, then, the need to run a whole bunch of background daemons in order for some "small and lightweight" text editors to run at all. (-:

* https://news.ycombinator.com/item?id=13056252

emacsclient is even more instant than vi, in my experience.

An old post I wrote (2006) on a way to improve emacs startup times by loading commonly used packages into your core for instant startup time:

http://web.archive.org/web/20060501032837/http://metashell.b...

Reply on news.ycombinator.com