I've been using VS Code for years now, and while it is measurably slower (I still use sublime to handle ad-hoc grepping log files as code just won't handle that, and scrollable, highlighting and multicursor is MUCH better than smacking bash pipes together), the batteries included "It just works" approach of code means I don't really see a reason to head back.
Maybe it's changed since the sublime 2/3 days, but the packages ecosystem always felt a bit unpolished and anemic.
The packages ecosystem is fine and always has been.
Because it works for me?
You seem to be acting like I'm an M$ shill out to convert people. In actually someone that uses both, stated my reasons for why, and enquired as to if my assumptions are based on outdated information that I may need to reevaluate in order to remain a competent developer rather than a tribalistic one such as yourself.
> The packages ecosystem is fine and always has been.
That statement is the exact same energy as "because it's cool". Every system is fucked in someway and ignoring those flaws in discussing them just belies denial or naivety.
One would never switch away from Sublime Text. It has always had a supportive package system since Sublime Text 2 and if you set it up with proper plugins it is a great IDE.
Where VS Code shined is with native JS support for beginner devs, as you said batteries included. But having already had that setup in Sublime Text (pre-VS Code) there would be no need to migrate editors.
no one asked
If I want to edit config files for basic things, isn't vim better? And if I want more power, isn't an IDE better? At this point I honestly like Atom more than Code. Even on Linux.
(I still use sublime to quickly edit text but I was really disappointed with their latest version)
>Maybe it's changed since the sublime 2/3 days, but the packages ecosystem always felt a bit unpolished and anemic.
As far as I can tell it's only gotten worse. The rise of Atom and then VS Code sapped a lot of the energy that went into creating plugins.