No argument there. But Sublime does support those languages. You just need to install the right plugin. The question is whether this should be baked in, or whe

No argument there. But Sublime does support those languages. You just need to install the right plugin. The question is whether this should be baked in, or whether it should be managed with plugins. There are lots of features people might want. Including them all creates a bloated text editor at worse, and a mediocre (IMHO) IDE at worst. I maintain that Sublime isn't and shouldn't be an IDE. So they're better off only including the features that are very widely needed for a text editor, and then supporting the rest as plugins. After all, isn't the ability to extend Sublime with plugins one of the biggest selling points? By being lean, it wastes as little computing power as possible on stuff you don't need, while giving you the ability to include virtually any functionality you do need. I get that sometimes plugins fall out of active development or are broken for unacceptably long periods of time. But if the feature is something that the Sublime dev team wanted to support, there's no reason they couldn't support it as a plugin. Baking it in doesn't solve this problem, but it does create bloat. I guess what I'm saying is: Why does language server support deserve to be baked-in more than any other feature? I have plenty of mission-critical needs that are supported by plugins. I don't expect them to be baked in just because they're important to me. I accept that the plugin ecosystem is the solution for my needs. What makes language server support -- or any other beloved functionality -- so special?