I don't hold allegiances to a text editor (c'mon, it just edits text!) so I switched from Atom for a while too: I was very impressed with it (it feels so snappy, and looks so cool!). It fell over on linting some of the ES7/8 things that we use in our code base - but as soon as they fix that I will give it another serious go.

I had the same complaints and just went with the excellent ESLint plugin with a ES2016/17 friendly config instead of the default vscode linting.

Agreed, it would be nice if the eslint module swallowed javascript linting errors for you... Also, would be cool if it defaulted to using an in-module copy of eslint with the airbnb preset as it's default if no eslint config file is found in the project/workbench.

IMO the Airbnb preset is too extreme / opinionated to use as a default ESLint config. Maybe something a bit more trimmed down would be reasonable.

The beauty of ESLint is that you can override it with your own settings. So you can use the AirBnB setting as the base and override the things that you want.

I know that, but I still think it's way too opinionated to be a base. My linter shouldn't annoy me by forcing me to do things that make my code less legible (like enforcing arrow-body-style) out of the box.

I liked them about equally, but Atom is really slow on my work computer and crashes on my laptop. VSC is much more stable.

Its slowness is the main reason I switched.

I've been switching back-and-forth between Atom and VSCode for several months. Both are great. I use them for app development. Vim for single file edits.

Agreed! That Cmd-P slow down was just a bit too laggy. Happy to see that resolved. Fuzziness seems improved too, but I didn't do a lot of thorough testing there.