this post was submitted on 26 Oct 2026
542 points (95.9% liked)

Programmer Humor

33796 readers
2197 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 3 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] rklm@lemmy.dbzer0.com 41 points 11 hours ago (5 children)

Linus introduced a race condition and a regression with a AI generated code, then handed off fixing the problem to someone else because he was going on vacation.

Fiasco might have been an exaggeration, but it's still pretty lame.

https://lkml.iu.edu/2610.1/13698.html

[–] mcv@lemmy.zip 19 points 6 hours ago

Race conditions are not unusual, and it was caught during review, so there's really no problem here.

[–] ChairmanMeow@programming.dev 67 points 10 hours ago (2 children)

This was caught during review, so nothing was "introduced" quite yet. And there's no indication that Linus wouldn't have produced a race condition (a notoriously more easy to miss kind of bug) without the use of AI tools.

It's only being exaggerated so much because he used AI.

[–] Fmstrat@lemmy.world 3 points 5 hours ago (1 children)

Yea he basically said "This seems to work but is slop, lead Dev, make it real."

[–] LH0ezVT@sh.itjust.works 9 points 2 hours ago

That is something I am surprisingly okay with. Quickly figuring out if something is feasible is good, and doing it in a back of the napkin style is the norm, even without LLMs. Of course then you need to do it properly, without falling into the trap of reimplementing the slop.

[–] tatterdemalion@programming.dev 15 points 8 hours ago (1 children)

I could attribute the race condition just as much to their use of the C language as to AI.

[–] ChairmanMeow@programming.dev 2 points 2 hours ago (1 children)

Race conditions I'm pretty sure aren't language specific. Rust can have them too.

[–] jjj@piefed.blahaj.zone 1 points 58 minutes ago

Yes, but the tools provided by Rust:

  1. Prevent most common ones via aliasing^mutability, Send and Sync marker traits, etc.
  2. Require explicitly marking the cases not handled by this, e.g. unsafe features require an unsafe {} block to be used.
[–] recursive_recursion@piefed.ca 17 points 10 hours ago* (last edited 10 hours ago) (1 children)

Great
This doesn't make me nervous at all...

Hide_the_Pain_Harold_András_Arató

[–] TrickDacy@lemmy.world 2 points 4 hours ago

It shouldn't, because it's a lie.

[–] TrickDacy@lemmy.world 0 points 10 hours ago (2 children)

Not what happened. I'm not digging it up but this story has been debunked repeatedly

[–] Artisian@lemmy.world 6 points 5 hours ago (1 children)

(you're welcome to just point folks to a debunking)

[–] TrickDacy@lemmy.world 0 points 4 hours ago

People are welcome to stop spreading the falsehoods. In every thread where this is said (including this one), the truth is pointed out but those spreading it couldn't care less. Just scroll. Others are pointing out the details here just like every other place.

[–] ThirdConsul@lemmy.zip 7 points 10 hours ago (1 children)

Literally you got hit with an linux mailing list saying this is what happened?

[–] TrickDacy@lemmy.world 5 points 4 hours ago

Those words don't make sense