4 ms·
>Not overall performance/memory so much as startup time Is this actually a problem, though? I typically use VSCode as a "focused" text editor; it's for working
by stu2b50 6y ago
>Not overall performance/memory so much as startup time
Is this actually a problem, though? I typically use VSCode as a "focused" text editor; it's for working on a codebase for a long period of time (relatively speaking). A minute or do startup amortized over hours of work is not much of a bother really.
For quick edits, vim is still my go to. Different tools for different needs.
- qppo 6y agoYes, because of how VS Code has evolved we're not using it for quick edits but as a front end to entire systems. If I need to check something quick in a remote session that is configured through some extension in VS Code without simple terminal access and for one reason or another I haven't left it idling all day, those times will hurt my productivity.