When I first started learning programming a bit over a year ago I had to switch from Atom to VSCode cause Atom ran terribly. Not a single flaw with VSCode for me so far.
I was using Atom for a while at my last job. I could sit and watch my battery percentage drop. It would absolutely destroy my laptop battery. It was so poor.
What plans does Microsoft have regarding GitHub's Atom text editor (which obviously overlaps in target user with VS Code)?
Ā
Developers are really particular about their setup, and choosing an editor is one of the most personal decisions a developer makes. Languages change, jobs change, you often get a new computer or upgrade your OS, but you usually pick an editor and grow with it for years. The last thing I would want to do is take that decision away from Atom users.
Atom is a fantastic editor with a healthy community, adoring fans, excellent design, and a promising foray into real-time collaboration. At Microsoft, we already use every editor from Atom to VS Code to Sublime to Vim, and we want developers to use any editor they prefer with GitHub.
So we will continue to develop and support both Atom and VS Code going forward.
A coworker of mine was lauding atom a few years ago, so I gave it a try. My first impression was that it was incredibly slow. I went back to Code pretty quickly. I'm pretty sure he uses Code exclusively now too.
Interesting thing - many portable applications, including VSCode and Atom, run in an environment called "Electron." Electron was developed as the runtime environment for Atom, or the "Atom shell." Atom shell - Electron.
It does show level of interest and commitment to a project. You could argue commits don't mean much for a mature project with relatively few bugs and a feature set that has an answer to everything (albeit some less than ideal)... But that isn't Atom.
156
u/[deleted] Feb 06 '19
[removed] ā view removed comment