Not to beat a dead horse, but: is there anything Atom does that VSCode doesn't already do better? Is there a reason to prefer it?
The VIM plugin for Atom is a lot more feature rich than the VS Code version.
amVim does it better, but is missing ; for repeating the last t or f command
This is getting like Windows vs. Mac. Doesn't make any sense.
Let VSCode be more optimized or technologically advanced than Atom like macOS might be compared to Windows, but without making that the reason why people should immediately switch to it.
You know, macOS and VSCode might be better, but there are people who are perfectly fine and more productive on Windows or Atom.
If you publish a new release and you happen to have a competitor in the same market that is currently eating your lunch people are naturally going to ask what makes it worthwhile to switch.
Sure, but that's not the tone used. Besides a few, most comments are dismissive of Atom and just point out how much better VSCode is and wondering why anyone would use Atom.
It's factions, like Mac vs. PC. There is no productive discussion, here.
I wanted to find out more about this release, and all I got was that I should switch to VSCode.
I'm saying "might very well be better"...
Sorry, English isn't my first language.
Simple answer: Plugins. It'll be the same answer every time this question is asked, for me.
As someone who doesn't see using typescript in the foreseeable future, and doesn't feel impacted by performance benchmark comparisons, VSCode doesn't seem to offer me any compelling reason to switch to it and go through reconfiguring another editor.
For example, VSCode is surely preferred more than Atom by Go developers because of the integration of the tools, Atom has the GitHub integration. And, maybe I am wrong, but I think that Atom has more people hacking it (making plugins and themes) than VSCode.
At this point, VSCode vs. Atom is like VIM vs. Emacs.
What I am saying is that VSCode vs. Atom is the same "war" that people who like to use VIM have against people who like to use Emacs. The people who defend Atom/VSCode do it the same way people defend VIM/Emacs, it doesn't matter if one was built with tiger's blood and the other with wolf's blood, the "war" between them is just an ideology, otherwise everyone would be ignoring one and using the other.
This opens two separate windows, each representing a project. Any editor can do this. Parent meant opening two projects in the same window.
This is the number one reason I do not use VS Code. I love having multiple projects open in the same window at the same time, accessible with cmd+p fuzzy search in Sublime.
I prefer thinking of codebases as folders in a file structure then as "projects", so I might be missing something obvious and is probably the reason I interpreted the parent comment's question the way I did.
This is something I do all the time in atom, and miss quite a bit when using vscode (for typescript).
Actually, that's what I thought when I tried using Sublime Text for a while. It took me hours of editing the JSON file to get it do look and behave like I wanted, while Atom has a very convenient GUI to change settings and install plugins and themes.
When I was finally done, I realized that the project tree view—if that's how it's called—sorts files with folders first like on Windows, and being on macOS it was too confusing for me since that was the only place throughout the OS where that happened.
To me, Atom is the solution to Eclipse's stagnation, Sublime Text's somewhat high price tag (I know we can afford it, I'm just saying), and personal preference, plus really good GitHub integration which for me is paramount.
I wouldn't define myself a uber-geek.