#Sublime text 4 code

I figured I'd wait until the non beta release, and try again.

I couldn't get the LSP to work for me for Elixir, so I ended up back on VSCode for now. I was formerly a paid user of ST3 before switching to VSCode, but gave the ST4 beta a try a month or so ago. 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.ДЄll 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. 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.

#Sublime text 4 code

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: