Earlier quoted context omitted.
About 10 seconds of startup opening a directory, from terminal to loaded workspace. I'm on a MacBook Pro (Retina, 13-inch, Early 2015). I have 76 community plugins installed.
76? Daaam. I thought I was overdoing it at 53. (If anyone wants to check: ls ~/.atom/packages | wc -l # minus 1 for the README Have you checked Timecop? (cmd-shift-p, "timecop") Might be a few you can do without.
Improving startup time in Atom with V8 snapshots
171–173 of 173 posts
Re: Improving startup time in Atom with V8 snapshots
#172Earlier quoted context omitted.
About 10 seconds of startup opening a directory, from terminal to loaded workspace. I'm on a MacBook Pro (Retina, 13-inch, Early 2015). I have 76 community plugins installed.
76? Daaam. I thought I was overdoing it at 53. (If anyone wants to check: ls ~/.atom/packages | wc -l # minus 1 for the README Have you checked Timecop? (cmd-shift-p, "timecop") Might be a few you can do without.
Re: Improving startup time in Atom with V8 snapshots
#173Earlier quoted context omitted.
That's fine. But myself and a lot of other people get a lot of "serious programming" done using the approach.
I don't really understand what the benefit of it is.
Have you seen a really seasoned vim user work? Purely from an efficiency point of view, vim/modal text editing is simply better than traditional text editors.