4 ms·
Never liked it. Takes an age to load up, but I guess once it's launched you can keep it open, so there is that. Then there's the MS telemetry to worry about, al
by spansoa 4y ago
Never liked it. Takes an age to load up, but I guess once it's launched you can keep it open, so there is that. Then there's the MS telemetry to worry about, although VSCodium[0] addresses that.
[0] https://github.com/VSCodium/vscodium https://github.com/VSCodium/vscodium
- unsupp0rted 4y agoMaybe it's because I'm on an M1, but I've never noticed the start time on VS Code. Does it take a while to load up? I start it maybe once every week or two (restart after updates) and keep it open after that.
- nevon 4y agoMaybe OP includes the startup of things like language servers in that time. In my experience VS code editor itself launches very quickly but that doesn't mean the full IDE is ready to be used. That said, I haven't experienced particularly long startup times either.
- jamesu 4y agoOn my current gen Windows 11 box it takes 5-6 seconds to launch and 2-3 seconds to finish opening a new window, which to me is pretty jarring.
- bmitc 4y agoThe telemetry can be turned off.
- LeifCarrotson 4y ago> Takes an age to load up, but I guess once it's launched you can keep it open, so there is that. I load up my editor once per day...if it's not still open from yesterday. You can CTRL+W to close a tab, but there's no reason to kill the whole app. I perpetually have a terminal, editor, and browser open. As long as CTRL+N or CTRL+T are instant, and it's instantly responsive after ALT+TABbing into the app, startup times are negligible/immaterial. I guess that sometimes I'm in VSCode, while other projects might be in Notepad++, Visual Studio, or various vendor-specific IDEs, but a project will last weeks to months. What's your workflow if not tabs and workspaces? Why would you ever close the whole application?