In the same way that good AI coding requires testing, project management and architecture, good AI writing requires you to fill the editor role. Be ruthless. Read line by line. By all means tell the agent to fix stuff. If you don't do this, your blog posts sound generic and lazy.
Claude Code LSP
11–20 of 43 posts
Re: Claude Code LSP
#12https://code.claude.com/docs/en/discover-plugins#code-intell...
Why are they doing this with a client plugin per server? It's antithetical to the whole point of LSP?
(At least they're reusing existing servers I suppose, but it stops me using whatever arbitrary one I want, as I could if there was just a single client with arbitrary configuration.)
Re: Claude Code LSP
#13LSPs 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?
Re: Claude Code LSP
#14I wish AI written submissions were banned.
Re: Claude Code LSP
#15I never got it working for even once. it's an epic failure on Anthropic
Re: Claude Code LSP
#16It's not as secret as they make it sound. Documented here: https://code.claude.com/docs/en/discover-plugins#code-intell... Also the post is definitely AI written partially, but still useful I suppose.
[deleted]
Re: Claude Code LSP
#17LSPs 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!)
Re: Claude Code LSP
#18This blog post is in the uncanny valley of "looks and sounds nice, but a bit too nice, could be useful, could be useless AI-slop, idk".
I’m pretty sure it’s AI written. It has the common AI style of, “That’s not just X! It’s Y!” Personally I find this annoying. I use AI for my writing but painstakingly try to maintain my own voice rather than lazily edit my prose into LinkedIn-speak.
I’m not usually bothered by this, but the style of this post made me feel mildly stressed while reading it. Not everything needs drama.
Re: Claude Code LSP
#19Not sure if it's Claude Code or golsp, but I had to uninstall the plugin. Regularly makes Claude Code crash with golsp going to 100% CPU usage.
Re: Claude Code LSP
#20I 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