Claude Code LSP • Hacker News Board

Re: Claude Code LSP

#41

Post by tempaccount420 » Mon, Mar 02, 2026, 2:02 PM UTC

xnorswap wrote: post #35

tempaccount420 wrote: post #13

LSPs suck. Compilers should be able to re-use their cache for queries, interfaced with through a simple CLI. They should not need more RAM than what the compiler uses. Most LSPs don't work well for big projects or with non-standard setups like Bazel. Edit: is this really so controversial it has to be downvoted?

One of the many advantages of LSPs is that they can continue to work even under the condition of compilation error.

This is not unique to LSPs, a good compiler will do the same.

Re: Claude Code LSP

#42

Post by _hao » Mon, Mar 02, 2026, 2:09 PM UTC

tempaccount420 wrote: post #13

LSPs suck. Compilers should be able to re-use their cache for queries, interfaced with through a simple CLI. They should not need more RAM than what the compiler uses. Most LSPs don't work well for big projects or with non-standard setups like Bazel. Edit: is this really so controversial it has to be downvoted?

It's sad to see that the sane opinion is so heavily downvoted.

LSP as a protocol is fine, but the actual technical implementation of JSON RPC is braindead. Only web devs that don't know anything about native code could devise such an abomination. What happened to plugins and dll's?

Re: Claude Code LSP

#43

Post by pancsta » Mon, Mar 02, 2026, 3:15 PM UTC

theknarf wrote: post #21

That is when the LSP works, now you've just introduced another thing that may fail.

For pytoy - maybe. Me personally, would love LSP-sourced completion in jetbrains. This dump bot suggests compile errors, APIs sucked out of thin air and other model-sourced nonsense. It does NOT read my code as I read and navigate code.

Id like LSP LLM in my IDE…