3 ms·
This comparison totally misses the the normal workflow for Emacs. Nobody normally starts an Emacs instance to edit a file and quits it afterwards. Typically yo
by nine_k 10y ago
This comparison totally misses the the normal workflow for Emacs.
Nobody normally starts an Emacs instance to edit a file and quits it afterwards. Typically you run Emacs in server mode, and use emacsclient to instantly open whatever files you need.
By the same token, somebody could give low marks to IntelliJ or Eclipse because it may take a good 20-30 seconds for them to load.
- Klathmon 10y agoIt also missed the mark with many of the others on that list. The line between editor and IDE is getting more blurred every day. I use Atom. It gets opened once a day and closed at the end of the day. It could take minutes to start for all I care. The amount of time saved by having the vast set of plugins, the customization, the tools, and more greatly exceed any kind of savings I'd get from faster startup time. People tell me how I'm wrong because my editor shouldn't use so much memory, I try to tell them that I'm more than happy with the memory usage for what I get and it runs fantastically on my computer. But at the same time, I use nano on remote machines for quick edits all the time. If it were slow to start, it'd be useless. And again if I were using an older PC with 4gb of ram and a 5400RPM HDD I might feel that the performance of atom is an issue, so I'd probably use something else. I'm glad there are so many options that all focus on different workflows and features. Just because one doesn't focus on the workflow you use doesn't make it wrong or worse, just worse for you.