I had many issues with the Python ecosystem. It's fairly fundamental to multi-project workflows to be able to use virtualenvs. Most of the community and tooling has centralised on them at this point. With VSCode you can launch the editor from a Terminal session with your virtualenv activated and it "Just Works". This will for the most part pick up your auto-formatter if you have one installed, that formatter will use the config in your project directory, etc etc.

With ST3 and the available plugins I was at the stage of editing my config every time I switched project to configure the paths, and it still didn't work as expected. Getting plugins to use config from a project directory rather than their own config was often impossible (e.g. black formatting plugin using pyproject.toml instead of the sublime black formatter configuration).

If I was working on projects with no other developers this might not be much of a problem, but working on a team where all canonical config is committed into the repo was essentially impossible.

Hmm I'm not super familiar with python ecosystem though I know some python devs at my company also use sublime.

In the JS ecosystem there are quite a few project specific configs (prettier, eslint, nvm) that seem to be read in by sublime and accounted for fine from project to project (possibly requiring package level config in some cases).

That’s the one reason above all others why I stopped using ST. I just couldn’t get it to work at all.

> I keep hearing the argument that the plugin community appears to be dead, but I've never had any issues.

As someone who moved from Sublime to VSCode, my experience was that I didn't exactly 'miss' crucial stuff in the former, but found things to still be better in the latter.

If I wouldn't be using VSCode, I'd probably not miss too much, but using it and its plugin ecosystem, it's hard to go back to Sublime as my main editor.