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.
Claude Code gets native LSP support
221–230 of 352 posts
Re: Claude Code gets native LSP support
#222It'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
#223Earlier 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.
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
#224What 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…
Re: Claude Code gets native LSP support
#225Earlier 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?
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
#226Re: Claude Code gets native LSP support
#227Re: Claude Code gets native LSP support
#228Earlier 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
Re: Claude Code gets native LSP support
#229I 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…
Re: Claude Code gets native LSP support
#230Maybe 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.