Hacker News new | comments | show | ask | jobs | submit login

This sounds entirely anecdotal. I haven't seen any significant exodus from Atom to VSCode among people I interact with. It seems like folks moving from other editors are about as likely to choose Atom as VSCode, and the things that used to lead to people choosing one or the other (i.e. performance, VSCode only opening one project at a time, the stupid huge icon bar in VSCode, etc.) have been resolved...Atom is now reasonably fast, VSCode can open multiple projects and you can close the stupid bar. I tried them both and ended up with Atom (and vim, where I actually still do most of my work, but new JavaScript projects are in Atom).

Atom still has more plugins, or did last time I looked (which was, admittedly, quite a while ago), and I think the ecosystem is a good indicator of how many people are actively using something.




The 2018 Stack Overflow Developer Survey [1] puts VSCode at almost double the number of developers compared to Atom (34.9% vs 18%). You're right about the package count: atom.io lists 7654 packages, compared to 6802 at marketplace.visualstudio.com, many of those being color themes (some seem generated and machine-published, too). That said, workflow for extension authoring in VSCode is amazing, the community is very much alive, and sometimes it almost feels like there's an "extension for everything". Quality may vary, naturally.

[1] https://insights.stackoverflow.com/survey/2018/


Wow, that's surprising. VSCode is not just (far) ahead of Atom, it's the leader on that survey. I'll have to give it another look. Last time I used it, it had far too many annoying characteristics.


> VSCode is not just (far) ahead of Atom,

Tutorial eco-system as well. When I jumped into JS development, all the getting started guides had Install VSCode as step 1.

So now I use VSCode.


> This sounds entirely anecdotal. I haven't seen any significant exodus from Atom to VSCode among people I interact with.

Were those two sentences in the wrong order?!




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: