4 ms·
There's latency in every part of the VSCode experience, not just on startup. And the startup delay is bad enough that it needs a harsher word than "latency". I
by ghusbands 5y ago
There's latency in every part of the VSCode experience, not just on startup. And the startup delay is bad enough that it needs a harsher word than "latency". I made the mistake of associating VSCode with *.txt files and had to quickly switch it to something else, as I was otherwise waiting each time I tried to glance at a text file. Programs like Notepad++ and Sublime Text come up instantly.
- cturtle 5y agoI agree that an electron-based editor is not as responsive as a native one, but the vscode devs have done a lot to make it as fast as it is. This talk [0] is a very interesting look into everything the devs do to make it startup quickly. [0]: https://m.youtube.com/watch?v=r0OeHRUCCb4 https://m.youtube.com/watch?v=r0OeHRUCCb4
- deleted 5y ago[deleted]
- abrowne 5y agoMy workaround for the startup delay, since I use it so much, is just to autostart VS Code on OS login, and never quit. I basically treat it as part of the OS, which I've started to prefer: my computer boots up to the editor, like opening a notebook, rather than an empty "desktop".
- e-master 5y agoFair point. I honestly do not experience any noticeable latency after startup, but that is probably because my dev machine is so powerful (12 core intel core i7-8700 3.2GHz, 64GB RAM). Coincidentally I do have it associated with txt files, and as I said before I can’t complain, it works marvelously. To be honest, I’m general I’m with the native app crowd whenever we discuss pretty much any other Electron app, but VSCode is an exception to me.