190

They got to him

top 50 comments
sorted by: hot top new old
[-] A_Random_Idiot@lemmy.world 1 points 1 minute ago* (last edited 1 minute ago)

how did linus torvalds, the man that would rageface scream at people for doing shit that was perfectly good, that he just didnt like, become the latest to bend over and butter his ass up for the AI cock?

[-] Kangae_Hishiryo@scribe.disroot.org 40 points 3 hours ago
  • "I only care about the final results and the correctness"
  • Looks inside
  • Final results are shit and code is just slop

Ahhh, I love AI /s

[-] chewypoops@lemmy.world 56 points 5 hours ago

His very first bug. Until this point, he had 100% error-free code. /s

[-] auzy1@lemmy.world 128 points 6 hours ago

That's what code review is for lol.

Where is the story here?

[-] ooterness@lemmy.world 26 points 2 hours ago* (last edited 2 hours ago)

LLMs make slop code faster than humans can meaningfully review. If you make LLMs the only review layer, then slop gets through because they have similar biases. Stop making slop.

[-] auzy1@lemmy.world 11 points 2 hours ago* (last edited 2 hours ago)

Cool assumption. But pretty sure it's not how things work at all but sounds great...

What actually happens is that you have a long list of multiple maintainers reviewing , and multiple branches for testing, and multiple layers of review too.

https://www.kernel.org/doc/html/next/process/maintainers.html . See that long list of maintainers for a start.

The actual policy is that everything ends up getting reviewed by a human. If I post a patch, it doesn't go straight to master

If it's not being properly tested and maintained, it gets dropped irrespective of what it is (remember devfs?)

Also, I'm not sure about the kernel specifically, but on projects I submitted code to, they often wanted complex patches broken down if possible.

[-] darkangelazuarl@lemmy.world 1 points 1 minute ago

Yes this means the review process is working. What is important to track is if LLM code causes a disproportionately large number of reviews or reviews that take longer because whoever generated the code doesn't actually know what it is doing. Hopefully not the case here but it does happen a lot with LLM coding.

[-] nilloc@discuss.tchncs.de 2 points 1 hour ago

XZ Utils made it past all those checks with malicious code from a human.

If they’d been more careful with their tarball commits it probably would have made it into the final and commercial distros.

It made into Homebrew for instance.

[-] auzy1@lemmy.world 8 points 1 hour ago

Correct me if I'm wrong, but that's not the kernel...

[-] Jakeroxs@sh.itjust.works 1 points 1 minute ago

You are correct

[-] p03locke@lemmy.dbzer0.com 9 points 3 hours ago* (last edited 3 hours ago)

Where is the story here?

"AI bad. AI do bad thing. Let's point and laugh at AI doing bad thing to delegitimize the technology in the public's eyes."

Meanwhile, at work, I interact with coding agents on a regular basis, and the results are pretty good. Then it goes through a local blind review by a more powerful agent, get pushed out to the company's code review agent, which is designed to be as critical as possible, check the ticket details, make sure everything matches what the design plan says. Depending on the repo, it might even go through an extra security review.

Then, because we aren't fucking stupid, it goes through the standard code review process by real developers. Sometimes they still find something, sometimes the agent code reviews found way more than a human can. Overall, I trust the current process over our previous one, where some guy spends barely two minutes looking at the code, rubberstamps it, and then QA discovers a few bugs that need fixing, because the damn code review wasn't as through and critical as it should have been.

[-] DementedSociety@lemmy.world 1 points 7 minutes ago

Thank you. This is a tool just like everything else. Garbage in equals garbage out. Generative coding in the right hands is an extremely powerful tool.

It's a difference between kids playing with fireworks. (Vibe coders that know nothing about software development) And rocket scientists at NASA building a new shuttle. (Real developers with controlled thoughtful AI workflows)

load more comments (1 replies)
[-] themachinestops@lemmy.dbzer0.com 54 points 6 hours ago

Linus probably uses AI effectively, but the question is how long until his skill deteriorate because of it.

[-] bamboo@lemmy.blahaj.zone 42 points 5 hours ago

I'd be more concerned with him and people of that generation aging out maintaining the project first, and newer generations not having the skills to begin with to carry it forward.

[-] some_kind_of_guy@lemmy.world 1 points 33 minutes ago* (last edited 33 minutes ago)

It's hard to believe he's not also thinking about succession and actively mentoring younger folks. The Linux kernel is his baby and he seems enmeshed enough on the community level. He's smart enough to not simply leave it to chance.

[-] NullCypher@lemmy.world 1 points 15 minutes ago

Tarvads successor has been named a long time ago, although I don't believe he's "young" but succession has been arranged for the Linux kernel.

[-] Evotech@lemmy.world 7 points 1 hour ago

Yeah. Linux maintenace becomes a paid subscription through the ai providers

[-] partofthevoice@lemmy.zip 1 points 1 hour ago* (last edited 1 hour ago)

I don’t know. People are creative. They’ll get burned and learn from their mistakes. At least, the ones who do will survive in their careers — then pass on the knowledge, repeat. So I imagine Linus will be replaced just fine when he retires. Wait until we’re 2 or 3 generations into using AI for development. It’s not like people are rocks; people don’t tend to just keep sinking.

[-] corsicanguppy@lemmy.ca 13 points 3 hours ago

of that generation

Ouch.

I think 'we' have about 20 years left in us. That's long enough for an entire new pet language to be born, surge, wane, and then die. ...or 27 entirely new web frameworks.

load more comments (1 replies)
[-] mynameisbob@lemmy.ml 53 points 7 hours ago

Amanda Caswell

Amanda Caswell is an AI journalist, certified prompt engineer, and technology commentator whose work and expertise have been featured on Fox News and CBS News.

[-] TrippinMallard@lemmy.ml 2 points 29 minutes ago* (last edited 26 minutes ago)

lol "certified prompt engineer" is a thing?

[-] honesthenery@thelemmy.club 30 points 7 hours ago* (last edited 7 hours ago)

certified prompt engineer 🤣

She gipity..... If not she mine as well be. We are yammering over a techno fart.

Amanda Caswell is an AI journalisturd, certified prompturd engineer, and turdnology commentaturder whose slop and nonsense has been featured on Fox News and CBS News.

[-] Buffalox@lemmy.world 94 points 10 hours ago

On Tuesday, he submitted a 10-patch series that delivered a 23-fold throughput improvement in a synthetic benchmark

Impressive, probably kind of like I can answer math questions very very fast.

Reviewers have since identified a race condition and raised concerns about memory reclamation.

That what I thought, I can answer math questions fast, but I don't claim to be able to answer them correctly.

[-] dgriffith@aussie.zone 78 points 10 hours ago

It seems that after the initial AI-generated patches there's been good discussion amongst the kernel devs about sorting out the issues, and a few revisions already that have tidied things up a bit.

So if after all that there ends up being a good performance improvement directly from a revised AI-created patch, what do I do with my pitchfork? Still raised angrily? Half-mast? Do I just let the torch smoulder?

[-] FauxLiving@lemmy.world 25 points 9 hours ago

You have to vow to use a new fork (which someone else should totally create) which does not contain this one specific patch.

[-] TrenchcoatFullofBats@belfry.rip 1 points 2 hours ago

Man, people really don't like systemd

[-] Calfpupa@lemmy.ml 18 points 7 hours ago

which someone else should totally create

Congratulations and thank you for volunteering! I look forward to your repo release. You are never allowed to stop maintaining this fork.

load more comments (2 replies)
[-] grrgyle@slrpnk.net 4 points 6 hours ago* (last edited 6 hours ago)

I'm still mad because the source is still tainted. You can guarantee that the contributions of unwilling people, { who 1) did not intend their work to be used by a for profit LLM, and 2) actively do not want their work used by an LLM at all }, is part of these changes.

Scraping isn't reading, etc etc. But also when did we just stop respecting people's wishes with the stuff they post? Like I made my own word scramble js script because a website owner didn't get back to me on whether I could use theirs, even though the script is right there to copy paste.

These companies just did the yolo founder-disrupter impatient thing when they could have been chill and done this all legit.

load more comments (2 replies)
[-] Diplomjodler3@lemmy.world 72 points 10 hours ago

So you're saying the review process worked as designed?

[-] Buffalox@lemmy.world 33 points 8 hours ago

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.

[-] db2@lemmy.world 18 points 6 hours ago

And particularly disturbing when the human understanding failure is from the original and lead Linux developer.

[-] Buffalox@lemmy.world 3 points 1 hour ago* (last edited 1 hour ago)

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.

[-] halcyoncmdr@piefed.social 2 points 3 hours ago

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.

[-] db2@lemmy.world -3 points 2 hours ago

the anti-AI circlejerk

I'd say do better but that's not likely to happen.

load more comments (2 replies)
[-] devfuuu@lemmy.world 13 points 7 hours ago

Only while there are still reviewers who care to review the slop. Which is a rare breed and will quickly soon vanish.

load more comments (1 replies)
load more comments (1 replies)
load more comments
view more: next ›
this post was submitted on 16 Oct 2026
190 points (89.9% liked)

Technology

88814 readers
4922 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. 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.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots


founded 3 years ago
MODERATORS