Claude Code LSP • Hacker News Board

Re: Claude Code LSP

#21

Post by theknarf » Mon, Mar 02, 2026, 1:00 PM UTC

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

Re: Claude Code LSP

#22

Post by jasonjmcghee » Mon, Mar 02, 2026, 1:02 PM UTC

For what's it's worth I never enabled anything and it proactively encouraged me to install various lsp plugins and prompted me to accept to install in most languages I've tried.

Re: Claude Code LSP

#23

Post by tlb » Mon, Mar 02, 2026, 1:02 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?

Compilers only do one file at a time, but an LSP needs to parse all the files.

Also, an LSP needs to update incrementally when you edit the file, not just when you compile.

Re: Claude Code LSP

#24

Post by re-thc » Mon, Mar 02, 2026, 1:03 PM UTC

dayglo wrote: post #20

I had great results using this for the past few months, it’s the same idea but implemented as an MCP: https://github.com/oraios/serena

Serena eats context for lunch (and dinner).

Re: Claude Code LSP

#25

Post by rossant » Mon, Mar 02, 2026, 1:04 PM UTC

AntiDyatlov wrote: post #14

I wish AI written submissions were banned.

Same. I can't this tone. I don't understand why modern LLMs can't show more variability in tone and writing style by default.

Re: Claude Code LSP

#26

Post by steeleyespan » Mon, Mar 02, 2026, 1:07 PM UTC

“ That's not an incremental improvement. That's a category change in how Claude Code navigates your code.”

Literally everything is written by AI now, even top HN articles.

Re: Claude Code LSP

#27

Post by sathish316 » Mon, Mar 02, 2026, 1:07 PM UTC

user3939382 wrote: post #4

I built this myself for my agents a long time ago from ctags.

I hope I’m not talking to an AI. Can you explain how you wire up ctags to Claude code and keep them upto-date?

Re: Claude Code LSP

#28

Post by JasonADrury » Mon, Mar 02, 2026, 1:09 PM UTC

AntiDyatlov wrote: post #14

I wish AI written submissions were banned.

There's a "flag" button. See an AI-written submission? Press it.

Re: Claude Code LSP

#29

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

MadnessASAP wrote: post #17

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?

But now your asking the compiler to also be a daemon. The compiler devs to add and maintain a not insignificant feature. The compiler to keep everything it caches for queries (whoops, look at that RAM usage climb!), and to cache data suitable for answering LSP queries (gosh! It's climbing a lot!)

Why does it need to be a daemon? Why isn't the on-disk cache enough? Running a compiler without making changes is instant. Many operations of LSPs feel slower than compiler's incremental compilation.

What cache is needed that the compiler doesn't already have?

Re: Claude Code LSP

#30

Post by colinhb » Mon, Mar 02, 2026, 1:12 PM UTC

From the intro section:

> That's not an incremental improvement. That's a category change in how Claude Code navigates your code.

I don’t know anything about the human(s) behind this project, assuming there are any, and intend no malice towards them, but when I encounter language like this, it just kills my enthusiasm for a project.

I wonder if that reaction is now, or will become, a majority one, and that AI flavoured language and products will face some audience headwinds if there aren’t indications of some level of human authorship / editing.