News for hackers. Stuff that matters.
Re:RipGrep musl binaries occasionally segfault during very-l... by gruntled-worker on Saturday August 01, 2026 @06:33PM (#49139176)
Until ~2000, "cellphone user in public" equated with "smug asshole." We're at that icky rejection stage with AI.

Two years ago, that writeup would have been viewed as a generous gift of time to the community. Now we can't be bothered to read through it because we know where it came from, and that it's just worth $0.06 in tokens. Another reason (I think) is because we know what it portends.

In a few years, digging manually through bugs will probably be a last resort. We'll go from sneering to yawning at the reports, as another AI agent reads them and verifies the fix. Just like we ignore compiler-generated assembly code and people on their cellphones.

Re:RipGrep musl binaries occasionally segfault during very-l... by doubletwoyou on Saturday August 01, 2026 @10:02PM (#49140369)
If we know ‘where it came from’ in the sense that the author couldn’t even bother writing anything themselves, why should other people bother reading this deluge of nonsensical strung together words?
Re:RipGrep musl binaries occasionally segfault during very-l... by gruntled-worker on Saturday August 01, 2026 @10:18PM (#49140454)
That's my point, we won't bother reading it. We'll let agents read it. People will eventually stop getting ticked off at this stuff.

One exception: if the model is poor or on 'low' and that leads to a crappy report. That's the equivalent of shipping performance-critical code built with -O0 in the compiler analogy.

Re:RipGrep musl binaries occasionally segfault during very-l... by krageon on Sunday August 02, 2026 @02:57AM (#49141836)
This is a crappy report, that's what is being discussed
Re:RipGrep musl binaries occasionally segfault during very-l... by gruntled-worker on Sunday August 02, 2026 @03:32AM (#49142003)
Is there any indication that it was a mini/fast/older model, or on a low effort level? My read of the reactions above is "ugh AI", not "ugh AI on the cheap". Not a single poster mentioned model or effort choice. It seems more like the usual irritation at "AI slop".

If you just mean that the result was technically incorrect or off, that's probably true, but it doesn't affect my argument.

Re:RipGrep musl binaries occasionally segfault during very-l... by monitron on Sunday August 02, 2026 @02:51PM (#49147199)
At work I am sitting on a small pile of incomplete/wrong/missing-the-point bug reports right now, all generated by Opus 5 on High effort. Even under good conditions, LLMs are still wrong quite a lot, and confidently so. I can see why you think instant dismissal of LLM generated work is shallow, but I think it's at least as shortsighted to assume that when it creates poor quality work it must be an old/cheap model, bad settings, bad prompting, etc.
Re:RipGrep musl binaries occasionally segfault during very-l... by gruntled-worker on Sunday August 02, 2026 @04:13PM (#49147862)
I'm not arguing that it's great. I'm arguing that the future of human work in this area will be limited to dealing with the cases when it isn't great, i.e. the pile on your desk. Choosing the best model and highest effort is the due diligence required to minimize the size of that pile.
Re:RipGrep musl binaries occasionally segfault during very-l... by RideOnTime22 on Saturday August 01, 2026 @11:00PM (#49140642)
It's less "can't be bothered to read through it because we know where it came from" and more "can't be bothered to read through it because of how word-salad it is"

Unless heavily prompted the written output is always so dense that you can barely understand it.