I haven't used Atom for more than a year. Is the performance better now? Faster than VS Code? Would it still crash if I accidentally opened a 100mb CSV file?
Atom 1.33
51–55 of 55 posts
Re: Atom 1.33
#52I use Atom daily for work, and I am overall satisfied with the editor and its ecosystem, in particular the mammoth improvements the core team has made toward addressing speed issues that plagued the editor in prior years. I haven't tried the new GitHub integration features in this package, but they seem cool. That having been said - Atom devs, if you're reading this, _please_ put a priority on fixing the auto-update…
That feature also doesn't work in Windows.
Re: Atom 1.33
#53Is Atom developed by microsoft now? It would be weird for them to invest in developing both editors in the long run, considering how much crossover the two have. Is the contributor community strong enough that it would keep going strong regardless? I'm not sure how many contributors were from Github vs elsewhere
In his Reddit AMA, the new GitHub CEO said he wanted to keep working on both going forward. https://www.reddit.com/r/AMA/comments/8pc8mf/comment/e0a235q
Re: Atom 1.33
#54I'll admit that I haven't used Atom in a very long time, but to be it just seems like a worse version of VS Code. I don't think I've ever introduced an Atom user to VS Code and they stick with Atom. Every one of them switches.
I lasted a few hours with VS before jumping back to Atom. Just couldn't stand it.
Re: Atom 1.33
#55I'll admit that I haven't used Atom in a very long time, but to be it just seems like a worse version of VS Code. I don't think I've ever introduced an Atom user to VS Code and they stick with Atom. Every one of them switches.
I want to love Atom. I really do.
But it's been four years and they still havn't fixed jump to definition in PHP.
Visual Studio Code has this, out the box. And it works really well.