Hacker News new | past | comments | ask | show | jobs | submit login

> Language server protocol is a specification

This is indeed the important bit, and out of process is in that regard merely a implementation detail (although a practical one).

Right now we have a situation where the N editors and M languages gives us NxM language-plugins matrix if we want complete support.

If a new editor or language comes along, the job to implement complete support across the line is astronomical (thus noone does). Right now you may even have to switch editor to get "full" support for a given language, if any support at all.

LSP replaces this with a much more manageable situation where we have N editors (with LSP clients) + M languages (with LSP servers), and that yielding a N clients + M servers solution-space instead.

Simplified a wee bit: One new editor only needs to implement a single LSP-client to support all languages with a LSP-server, and one new language only need to implement a single LSP-server to be supported in all editors which already has a LSP-client.

This really is a revolutionary change, and I'm surprised how little attention LSP has gotten in the grand scheme of things.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: