Tangental, but my LSP config breaks every few months. I don't bother to fix it anymore, I open an LLM in ~/dotfiles and complain until it works again, usually in a few minutes. What's interesting is observing how much work this takes. (it gives me much more empathy toward my past self; how was a clumsy human supposed to know and reason about these things!?, especially when I hadn't touched the configs since a few mon…
Grep beats LSP? Why coding agents ignore your fancier tools
11–20 of 80 posts
Re: Grep beats LSP? Why coding agents ignore your fancier tools
#12Re: Grep beats LSP? Why coding agents ignore your fancier tools
#13Re: Grep beats LSP? Why coding agents ignore your fancier tools
#14Tangental, but my LSP config breaks every few months. I don't bother to fix it anymore, I open an LLM in ~/dotfiles and complain until it works again, usually in a few minutes. What's interesting is observing how much work this takes. (it gives me much more empathy toward my past self; how was a clumsy human supposed to know and reason about these things!?, especially when I hadn't touched the configs since a few mon…
This seems like the LLM is vastly overcomplicating things. My entire Neovim config is a single 500 line init.lua and this is enough for LSP to work.
Re: Grep beats LSP? Why coding agents ignore your fancier tools
#15It is astonishing how easy it is to see the AI hand at work in the writing. Really, it is almost impossible not to see. I don’t get how these people feel it is appropriate to pass off slop like this and not even bother to edit it. Just painful to read.
> Avoid generic tangents.
> Please don't post shallow dismissals
> Please don't complain about tangential annoyances—e.g. article or website formats, name collisions, or back-button breakage.
See: Hacker News Guidelines
Re: Grep beats LSP? Why coding agents ignore your fancier tools
#16Re: Grep beats LSP? Why coding agents ignore your fancier tools
#17There’s been an interesting co-evolution that I’ve been experiencing with Claude Code. I’ll ask it to do a task, I’ll watch what it’s doing (often lots of find and grep and ripgrep) and then after the task is complete I’ll ask it if there are any tools that would’ve made the job easier. This has led to tools like fzf and others (notmuch for indexing email, for example). I’ve then taken those tools and figured out how…
Re: Grep beats LSP? Why coding agents ignore your fancier tools
#18"Training support is a hypothesis consistent with these results, not something this study proves."
I understand it, but I find the wording very unnatural. To improve readability I would have written it in the active form:
"We cannot prove training explains this result, but this fits the data best."
Re: Grep beats LSP? Why coding agents ignore your fancier tools
#19It is astonishing how easy it is to see the AI hand at work in the writing. Really, it is almost impossible not to see. I don’t get how these people feel it is appropriate to pass off slop like this and not even bother to edit it. Just painful to read.
Shut up. Just shut up. > Avoid generic tangents. > Please don't post shallow dismissals > Please don't complain about tangential annoyances—e.g. article or website formats, name collisions, or back-button breakage. See: Hacker News Guidelines
I’ll point out you also violate this guideline.
Do you seriously read the article and not see that it is extremely low signal-to-noise? And full of non-sequiturs and strange unnecessary clarifications? And passed off as a research project.
“Claude, write an article about why agents use grep instead of LSP”
This would have saved everyone the pain of reading this.
As another user pointed out: “Training support is a hypothesis consistent with these results, not something this study proves.” is not a sentence a human would write, nor is it a sentence that a human should ever be made to read. I apologize for reproducing it; the article is chock full of these “gems”.
Re: Grep beats LSP? Why coding agents ignore your fancier tools
#20This article presents some evidence for why Grep might work better but I don’t think it does a great job of explaining why it gets chosen - is it something that was intentionally reinforced during training or was it just because LSP is harder to train on because it’s usually hidden behind some IDE interface There’s no reason why you couldn’t write a search tool that e.g combines LSP and grep. Or ast-grep, for that ma…