Atom and VS Code only share the Electron environment, but the actual way they've implemented the editor rendering and interaction is completely different. Basic

Atom and VS Code only share the Electron environment, but the actual way they've implemented the editor rendering and interaction is completely different. Basically, all that VS Code shows is that it's not the JS/Chrome environment that's the bottleneck, it's the editor implementation itself. There's some discussion in this Atom ticket: https://github.com/atom/atom/issues/10188 https://github.com/atom/atom/issues/10188