...what Microsoft really owns is Github! Each editor appeals to a different class of users. As long as they make sure they both integrate better with Github than with competition (GitLab, Butbucket etc.), then they bring and keep users to their GitHub platform!
But if some of Atom's "hackability spirit" would spill over to VSCode we'd appreciate it ;) It may be significantly more usable, but it lacks that "man, it feels just feels hackily good, like an Emacs for the 21st century" of Atom.
From what I have tried, VS Code doesn't allow access to the DOM or give much of an API to modify the visual layer. This makes it very difficult to draw visualizations on top of the editor. It also does not allow plugins to go beyond the standard tab-document metaphor.
For example, students of mine tried to re-implement Patchworks  as a VS Code plugin. Didn't seem feasible. They have been very successful in building it in Atom though. As another example, I tried to make a tool that displays a call graph visualization on top of the editor . But again, this was easy in Atom but I couldn't figure it out in VS Code.
Please point me to any documentation or examples of how to implement features like those.
You can find some plugins that could make Atom seems completely different, but most of the VSCode image you can find on the internet remains similar.
Just like with Emacs you can rewrite Emacs itself. And all of the changes in Atom do not require restarting, while some of the VSCode plugins require to restart the code editor (but might explain a little bit why VSCode is faster).
Resource consumption is less of a concern to me than general 'snappiness'. Since I have a bunch of RAM, go ahead and use it all if I can have a good experience.
I don't actually use Atom, though I use Sublime full time. My biggest reason for not being able to use Visual Studio is that all functions, be it fuzzy search, regular text search, navigating tabs, even entering a character carries the load of the VSCode IDE. It must parse each character for chances to present additional information, which is great if that's what you want.
Subjectively, I find VSCode too laggy to work at my usual pace.
Atom is definitely NOT an improvement in that regard. Microsoft optimized the shit out of the parsing bits of VSCode, moving as much as they could into C++ Node extensions for speed and responsiveness. As Electron apps go, VSCode is tense nearly to the point of rupture. Atom has made great strides, but afaik is still not there yet.
I wish we had found a way to integrate these review features in to git itself so this feature would work no matter where you hosted your git repo rather than having every text editor have to implement proprietary apis.
I hear this a lot, and I still don't really get it - git is already decentralized! And not just federated, but truly decentralized where everyone has their own copy of the data. An issue tracker built on top of the git protocol, where issues/PRs/whatever arbitrary other rich text content you want lives inside the .git directory alongside the source code would be much more in the spirit of git. And you could build a pretty modern web interface on top of that!