248
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 16 Oct 2026
248 points (91.1% liked)
Technology
88814 readers
5743 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 3 years ago
MODERATORS
So you're saying the review process worked as designed?
Maybe it did, but apparently the code was not properly reviewed initially, so there could be other hidden problems.
Of course that's the same for human made code, but there's a problem in only judging code from how it performs, and not actually understanding the code. And that seems to be the situation with a lot of AI code.
And particularly disturbing when the human understanding failure is from the original and lead Linux developer.
100% that is the worst place to have the problem originate.
I have rarely disagreed with Linus Torvalds on things regarding the kernel, and maybe I'm wrong, but I strongly disagree with him on this issue. Contributing code nobody understands cannot be a good thing.
You people act like Linux adopted an all-AI pipeline.
Is it an understanding failure, an unexpected interaction, or just an existing issue now exposed? A 23x performance increase could very well expose an existing race condition that systems weren't fast enough to run into.
People make mistakes. Software bugs existing at all is proof of this. This is certainly not the first time a change Torvalds approved has an issue, and it won't be the last.
There's a reason code is reviewed, and there's a reason people still go through after it is approved and verify. The process is working exactly as designed, the way it has for decades before AI coding.
Expecting absolute perfection is ridiculous, the anti-AI circlejerk acting like only AI fucks up just makes them look ridiculous. Any developer could have developed this fix, and there would be no article. Nothing in this issue is specific to AI usage and treating it like it is somehow special just undermines arguments against AI slop and vibe coding in general.
I'd say do better but that's not likely to happen.
So, let me get this right. You're disapproving on how things were handled based on your speculation of how it went?
Not based on speculation, based on numerous analysis of the problems with using AI code you don't understand.
Clearly Linus failed to understand the code, otherwise he wouldn't have suggested it for submission.
You seem to have a problem with criticism of Linus, is it a religious thing?
Of course of course. How dare you blaspheme against our Lord and Saviour, filthy infidel!
But anyway, I'd like to be as enlightened as you. Could you name any of those numerous analyses that detail exactly what Torvalds did and what he failed to understand?
Only while there are still reviewers who care to review the slop. Which is a rare breed and will quickly soon vanish.
I bet some projects will get more tolerance and love than others, based on value and utility. The kernel will get more, and Systemd will get less.
Yes, but it's bad because software has bugs.