For instance, I butted heads with the maintainer of ST's Python plugin over the need to have independent per-project settings. This is critical for me as I work on several codebases that have different Python versions, virtualenvs, installed packages, testing frameworks, etc. In contrast, VSCode makes it trivial to use ~/envs/project1/bin/python3.6 for one project and ~/envs/project2/bin/python2.7 in another.
I fought long and hard to try to get ST to be usable in that scenario but eventually gave up and went back to Emacs. About a year ago I tried VSCode and found that it was my medium medium between nearly as configurable as Emacs (for my purposes) but as pretty as Sublime Text. Either way, I can't see paying for ST anymore when I have a couple of good FOSS editors that may be a bit slower but don't take nearly so much work to whip into a usable state.