Hello, one of the LSP contributors here. Just wanted to share my thoughts on why LSP as an open source plugin has more benefits than getting first class suppor

Hello, one of the LSP contributors here. Just wanted to share my thoughts on why LSP as an open source plugin has more benefits than getting first class support from ST devs. Cons of getting first class support from ST: - ST is closed source. That would mean that the LSP source code would be closed source too and that would not allow other people to contribute to it. - Implementing the LSP client in c++ won't make the user experience faster. The speed mostly depends on the speed a language server returns a response to the LSP client. - ST devs would shift focus on implementing the LSP spec which is mainly driven by Microsoft and the spec is somewhat driven by VS Code functionality. So ST would chase after offering the same functionality as VS Code, but then always be a step back. Having LSP as a plugin allows the best for both ST users and ST devs. It allows ST users to contribute to the LSP plugin, while ST devs can focus on making ST more awesome on their own way and adding new API-s. All I can say is that LSP already has first class support, because the ST devs have specifically expanded the API to allow LSP to implement certain features. :)