[wbond]

We looked into the protocol, but unfortunately it made a number of poor architectural choices that leads to many language servers not implementing the protocol properly. This effectively requires custom integrations for most language servers. That wouldn't make sense to do in the core of the editor, since we'll never be primary users on the vast majority of servers.

The open source model makes sense since it will need to have tweaks and fixes to support various language servers. That combined with a very small development team (six engineers across our two products), would probably lead to slower development, and it would be tied to the release cadence of the main product.

[modeless]

That's unfortunate, but I still think it would be best if you could at least add support for one or two servers in the core, with extensibility for others. Or officially adopt and support the community LSP plugin. My experience with the community LSP plugin has not been good, and it almost led met to switch to vscode. (That and debugging which is a whole other can of worms.) I really think working on LSP would be a better use of your time than continuing to improve the current fuzzy indexing engine.

[ben-schaaf]

The problems you're likely had with the community LSP plugin were due to a lack of APIs provided by ST. For ST4 we've worked together with the community LSP plugin authors to properly support it.

[hn8788]

That makes sense, I didn't know how small the team was. Thanks for the response, looking forward to ST4.