4 ms·
Long time Atom user here as well. When I first tried VS Code, the first thing that I noticed was how much better the performance was compared to Atom. From gen
by lewisl9029 11y ago
Long time Atom user here as well.
When I first tried VS Code, the first thing that I noticed was how much better the performance was compared to Atom. From general snappiness of basic editing tasks to startup times to working with large files, VS Code simply outperformed Atom across the board according to my brief unscientific observations.
At the time, I ended up sticking with Atom mainly because VS Code wasn't open source and lacked extensions, but it looks like this release addresses both issues.
Well done, Microsoft. I'm definitely going to give VS Code another serious look and recommend other Atom users to do the same.
- plexicle 11y agoThis is spot on for me as well. I always wondered how VSC was so much faster given that they are both on top of Electron. In either case, this is all great news.
- ehaughee 11y agoElectron, iirc, is just the UI layer. Atom actually has a lot of code written to render, edit, and rerender text (they were initially using React at one layer of the process). I can't find it now, but there was a good blog post from the Atom team that discussed their efforts in detail. So I guess I'm trying to say that I believe the code handling the slow parts is predominantly unrelated to the UI layer. Also, iirc, VSCode's editor is based on Monaco (http://www.zdnet.com/article/microsofts-browser-based-dev-toolbox-how-monaco-came-to-be/ http://www.zdnet.com/article/microsofts-browser-based-dev-to...).
- spleeder 11y agoThis is my experience as well. I am really impressed at how VS Code as no problem working with large and minified files.
- dancsi 11y agoIt really depends on how large is considered large, since for me it crashes when opening a 60MB XML file...