Live data from Hacker News

Claude Code gets native LSP support

github.com

221–230 of 352 posts

Re: Claude Code gets native LSP support

#221
post #175

Earlier quoted context omitted.

Jetbrains seems a bit lost these days. Look at that very recent screw up [0]. I thought about moving after 10+ years when they abandoned the commit modal, and jacked up the plan prices, but I barely understand how to commit things in Vscode anyway. Let's see in 2026. [0] https://blog.jetbrains.com/datagrip/2025/12/18/query-console...

The commit workflow was what kept me locked in to the ecosystem for so long. LazyGit was so good that it convinced me I didn’t need JetBrains anymore. If you love the workflow with JB for commits check out LazyGit. It’s a TUI so you can use it in any editor without much friction.

Fortunately JB broke that addiction for my by first moving the commit dialog behind an option, and then removing it completely. If I have to learn a new workfrow, I might as well learn a new tool

Re: Claude Code gets native LSP support

#222
I hate everything about the Claude code plugin system. They saw GitHub Actions supply chain Fiasco and said: great let's add hallucinations on top.

It's that bad. It's embarrassingly bad.

No lock files. Nothing. And then most plugins in turn install MCPs from pypi with uvx so you have two layers of no pinning.

It's a supply chain nightmare. It's so bad that I'm ashamed for our industry

Re: Claude Code gets native LSP support

#223
post #203

Earlier quoted context omitted.

Graphical interface won't work well inside WSL, that's why I dropped my subscription on GitKraken and start using lazygit. lazygit simply works in almost any environment, and it works extremely well even if you are not into terminal stuff.

Really? While there its certainly slightly annoying because they have the "double menu bar" if they use a non-standard one like the jetbrains ides do... I feel like wsl gui support has essentially become a "solved issue" for a while now.

Yes and no, GitKraken actually have a graphical interface for WSL (or Linux generally), but it is barely usable as the WSL-g does not really work well. It's blurry for Hi-Res screen and the performance is like hell.

I would never try running any graphical stuff in WSL anymore, not worth it. VMWare with a graphical installation of any Linux system would be a preferred choice as I'm testing lately.

Re: Claude Code gets native LSP support

#224
post #76

What boggles my mind is. I've been using OpenCode [1] which had this future for at least 6 months. I sometimes baffled by the slow progress of closed source software. Also highly recommend OpenCode you can also use it with your Claude subscription or Copilot one. [1]: https://opencode.ai/

I must be doing something wrong, because I can't get OpenCode to actually do anything useful, and not for lack of trying. Claude code gets me great results instantly, opencode (if I can't make it talk to a model, which isn't easy for Gemini) gets me… something, but it's nowhere near as useful as claude code. I don't know why there is so much difference, because theoretically there shouldn't be. Is it the prompt that…

There’s a ton of difference provided on top of the LLMs, especially the tools that allow LLMs to engineer their own context, validate generated code, test generate code, research code bases, planners, memory, skills, etc. The difference is night and day: like a brain in a closed jar versus a brain in a mobile human with eyes, ears, mouth and hands.

Re: Claude Code gets native LSP support

#225

Earlier quoted context omitted.

Jetbrainz needs to give up on Junie and their in house ai and focus on integrating with the established tools. If they don’t, VS code will consume them.

Is there something with the Claude code plugin for JB IDEs you don’t like? Is there something the VSCode Claude Code plugin does better?

I can’t speak for Claude, but Gemini is laughably bad. Like, does someone who develop this shit ever tried to use it? Is it all crab hands that only use mouse? It’s a single line change to switch focus to THE ONLY INPUT on a tool window, but no, you have to use a shortcut to switch to Gemini window and then MOVE YOUR MOUSE across the screen to select input or press tab like 5 times. Embarrassment.

VSCode? Select AI view via shortcut or CMD + P and you’re done. That’s how you do it.

Re: Claude Code gets native LSP support

#228
post #221
post #175

Earlier quoted context omitted.

The commit workflow was what kept me locked in to the ecosystem for so long. LazyGit was so good that it convinced me I didn’t need JetBrains anymore. If you love the workflow with JB for commits check out LazyGit. It’s a TUI so you can use it in any editor without much friction.

Fortunately JB broke that addiction for my by first moving the commit dialog behind an option, and then removing it completely. If I have to learn a new workfrow, I might as well learn a new tool

Currently the plugin version still works but they made it clear it will be unmaintained in the future.

Re: Claude Code gets native LSP support

#229

I really can't understand why JetBrains hasn't integrated its refactoring tools into the AI system. Really missed the boat on making their platform transformational for AI coding. Imagine how much smaller the context would be for a tool that renames a function than editing hundreds of files. This LSP support is a good start but without the mutation functions it is still pretty lackluster. Plus LSPs aren't as good as…

They’ve also dropped a huge ball with resisting LSP for Kotlin, thinking that they could lock developers into their ecosystem. Well, now (hopefully) it is too late, karma is a b*tch.

Re: Claude Code gets native LSP support

#230

Maybe I'm the only one, but does anyone else have an issue on macOS where Claude Code never updates itself automatically and you always have an error? I guess it's in times when I leave the CLI tool running and an update comes in overnight. But the alert seems to indicate it should update and fails.

I removed the locks directory which fixed it
Post reply on HN