(no title)
v-yadli | 3 years ago
This is not always the case for existing servers. Semantic highlighting wasn't in the protocol until 3.0 (iirc), and many servers have extra non-standard endpoints. So the real world situation is that there's a core feature set allowing M+N, and additionally, custom endpoints and features requiring MN.
Nevertheless the non-standard MN endpoints at least follow the "shape" of LSP -- same communication channel and message format, and that makes MN much easier than before already! As the core protocol evolves, more MN features will be decoupled to M+N.
jez|3 years ago
There are already a more than a couple LSP features I wish existed, but in the mean time it’s good enough to have the (typed! and using rich data structures!) RPC endpoints exist for enterprising users to wire up to their IDE’s presentation layer.
orlp|3 years ago
v-yadli|3 years ago
- Programming based on fragments, not documents (e.g. LEO https://leoeditor.com/)
- Live programming (e.g. smalltalk environments)
- ... where certain actions are not available, e.g. a PL geared towards speech recognition may not support "hover"
But on the other hand, these are not well-aligned with current text editors (text based, has a cursor, organize info as documents etc.)
So languages are one side, editors are the other.
oblio|3 years ago
Innovation could just happen at a higher level.