I would expect that with the new TreeSitter parser (and other improvements) Atom now feels faster than VS Code. Is that the case?
Atom 1.33
31–40 of 55 posts
Re: Atom 1.33
#32I'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 switched, after a prior history of many other editors, to VSCode, and then to Atom. One main reason: the vim plugin. The VSCode one was (is?) just not good. Atom's is quite good.
VSCode is better for most people; it's a great editor, and does more out of the box without configuration. However, if you're someone who DOES feel the need to tweak everything until it's just right, VSC doesn't hold up. JSON configuration is just clunky. Atom is, at least in some aspects, scriptable without the need to build a full plugin (though it's certainly no emacs), and that's quite valuable. And, when you introduce the atom-ide package, the gap in completion and debugging functionality between the two gets quite a bit smaller.
Also, anecdotally, Atom seems to have had better performance across my machines; especially on lower-end hardware. I'm only working on small-medium sized projects, so this might just be me.
Re: Atom 1.33
#33I'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.
IntelliSense. Definitely my reason for not going back.
atom-ide (https://ide.atom.io) brings a lot of the great intellisense features over to Atom. It's most likely not completely on par, but as far as I can tell and based on my own usage, it's beyond good enough for most work.
Re: Atom 1.33
#34I'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 switched, after a prior history of many other editors, to VSCode, and then to Atom. One main reason: the vim plugin. The VSCode one was (is?) just not good. Atom's is quite good. VSCode is better for most people; it's a great editor, and does more out of the box without configuration. However, if you're someone who DOES feel the need to tweak everything until it's just right, VSC doesn't hold up. JSON configuration…
Atom's vim bindings are great. They lack just one command that trips me up from time to time: :u.
Yeah, I can get by with cmd+z, but it would be nice not to be forced to context switch when I'm thinking in ex-mode.
Re: Atom 1.33
#35How does performance compare with VS code? How does Vim mode compare?
The vim plugins in atom completely blow VSCode's out of the water. It's split up into two packages ('vim-mode-plus' for most of vim, and 'ex-mode' for handling ex commands), but they work together very well.
In my experience (which certainly does not reflect everyone's), Atom wins in performance these days, too. Startup time is a bit slower, but once it's running it's quite snappy. It feels... less like a webapp than VSC does, if that makes sense.
Re: Atom 1.33
#36I 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…
$ brew cask reinstall atom
...
atom was successfully installed!Re: Atom 1.33
#37Earlier quoted context omitted.
I switched, after a prior history of many other editors, to VSCode, and then to Atom. One main reason: the vim plugin. The VSCode one was (is?) just not good. Atom's is quite good. VSCode is better for most people; it's a great editor, and does more out of the box without configuration. However, if you're someone who DOES feel the need to tweak everything until it's just right, VSC doesn't hold up. JSON configuration…
Atom's vim bindings are great. They lack just one command that trips me up from time to time: :u. Yeah, I can get by with cmd+z, but it would be nice not to be forced to context switch when I'm thinking in ex-mode.
Huh, I didn't even know there was an ex command for undo. Neat. I imagine that would be a pretty easy PR to the ex-mode package, if you're up to it ;)
Re: Atom 1.33
#38I 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…
I had the same issue. I’ve found that if it the update hangs, I can quit atom and wait a few moments and the update will go through.
Re: Atom 1.33
#39Is 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
Re: Atom 1.33
#40I'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.
vscode gives me the impression of a shitty microsoft product.
[deleted]