97 ms·
For me Emacs opens up in about 2 seconds and it's ready to go and print text input in scratch buffer. I am on 2015 MacBook Pro 13" with i5.
by Philipp__ 10y ago
For me Emacs opens up in about 2 seconds and it's ready to go and print text input in scratch buffer. I am on 2015 MacBook Pro 13" with i5.
- braveo 10y agoThat's been my experience as well, although that's still too slow for my tastes as a vim user. But I definitely don't ever recall it being 8 seconds, that feels like either an exaggeration or someone working on a potato.
- klibertp 10y ago> that feels like either an exaggeration or someone working on a potato. Haha, no. It depends on what you use Emacs for. Remember the old joke about Emacs being a great OS? The reality is that Emacs is a great computing environment for almost anything that deals with text and even for some completely unrelated things. If you want a cross-platform GUI then Emacs Lisp may be one of the choices available. This caused "plugins" - Elisp applications - to flourish and over the years a lot of code was written. Long story short, I have ~640000 (not a typo) lines of Elisp in my ~/.emacs.d/ alone, not counting the built-in Elisp libraries. It takes time to load that much code, even if it's byte-compiled beforehand.
- braveo 10y agofair enough, I've never been able to stay with emacs long enough to collect the plugins. The 1-2 second startup was slow enough that I couldn't even stay with the Emacs evil mode.
- eric_the_read 10y agoFor me, it takes <700ms, but that's because I leave it running all the time and call emacsclient from the command line.