News for hackers. Stuff that matters.

A comment on Why LSP?. Parent comment

Re:Why LSP? by zozbot234 on Monday April 25, 2022 @05:17AM (#31152154)
> Shared data structures are everything in this problem, yet the LSP model effectively forbids all shared state between backend and frontend.

The "shared state" in this context is IDE program text, and analyzer diagnostics. Copying those across address spaces and keeping them in sync is super fast, the overhead is too low to matter.

[ Parent | on HN ]
Re:Why LSP? by mike_hearn on Monday April 25, 2022 @07:34AM (#31153092)
And auto-completion suggestions (potentially means switching context back and forth on every keystroke), and inline editor hints / styling / folding regions, whatever is being changed by refactorings and so on.

Recall that most analysis is done async, so results arrive at different times. Even if you're not doing anything then, your IDE/backend will be context switching back and forth as stuff arrives to be rendered.

In the limit this degrades to the backend being the entire IDE and the frontend being just an translator between the OS IO system a stream of JSON rendering commands.

[ Parent | on HN ]