Fork me on GitHub

Hi, @seancorfield - I know you probably posted this in another place, but can you share what made you move from Atom to VSCode, apart from "better support"? I'm asking because as we're trying to keep the editor alive and well, and in the process we're modernizing some tools, I want to try attacking some of the worst "pain points" that Atom currently have too, if possible.


The much wider range of extensions, the faster development/bug-fix cycle, and it coincided with the Portal extension for VS Code -- which I rely heavily on. The Atlassian extensions are also critical to my workflow now (Jira and BitBucket). Calva generally having much richer functionality and, again, a faster dev/bugfix cycle. I've also since moved completely to Windows/WSL2 so VS Code's remote development model is critical to my workflow as well now.