2 ms·

I don't have a comparison that you are looking for, but I will say that I recently did an experiment. I timed (by hand using an app on my phone) the total time

I don't have a comparison that you are looking for, but I will say that I recently did an experiment. I timed (by hand using an app on my phone) the total time I spent "waiting" for Atom to launch over a full work week. It came to about 80 seconds. 80 seconds in chunks of like 10 seconds or so mostly at the start of my day. I have a shitload of plugins and my Atom instance loads significantly slower than my coworkers, but even so 80 seconds a week is nothing compared to the time savings that atom brings me. Yes, it could be faster, but it won't materially improve my experience.

setr 9y ago
Tbf the point of startup time isn't the actual time cost: its rarely significant; even a 5 minute startup is only 5 minutes for an 8-hour workday. But it feels absolutely awful to have to wait 5 minutes to start doing something useful. Especially when its not necessary, and when you've got alternatives that start up instantaneously (ie basic vim install). The problem is in that transition from 10ms wait to 10s wait; the difference is immense. And of course, theres the idea that an order of magnitude difference isn't just an order of magnitude difference; it can enable entirely different paradigms and workflows. In the fashion that the shifts in web-capabilities correspond at least to a degree to the shift in network capabilities. Streaming doesn't make sense on a 10kb/s connection, but on 10mb/s the whole world changes