
Having LSP as a plugin allows the best for both ST users and ST devs. So ST would chase after offering the same functionality as VS Code, but then always be a step back. 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. The speed mostly depends on the speed a language server returns a response to the LSP client. Implementing the LSP client in c++ won't make the user experience faster. That would mean that the LSP source code would be closed source too and that would not allow other people to contribute to it.


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.Ĭons of getting first class support from ST:
