Interesting how Microsoft manages to do in TypeScript stuff that Github not even with C++ managed to (according to the interwebs), regarding performance.
Now that they are also part of Microsoft, maybe they could share some information among them.
For example- it's not uncommon for Vim mode in VSCode to just stop functioning for 5-10 seconds on large projects while other addons continue operating.
I keep switching back and forth, primarily because VSCode's performance wins are so deceptive- it will feel amazing and look cool on some things, then in completely unexpected places just absolutely shit the bed. So I hop back and forth, and have even started working on building my own plugins for VSCode to do the things no one's added to it yet that Atom has addons for.
https://code.visualstudio.com/docs/editor/editingevolved#_go...
What makes you stick to Atom? I switched to VSCode due to Atom's terrible performance when opening huge files.
Really it took me many months of tweaking to get Atom to be a daily driver - I don't want to do it again soon
OTOH vscode does have a way to do this using a `launch.json` file which is flexible enough to add custom debugging profiles for a single project and it can be stored directly in version control. I tried the editor out because of this one feature alone in order to debug node and haven't looked back.
For everything else these days I use VSCode.