Linus admitted he uses LLMs sometimes, so now the most trustworthy developer in the history of computers is now being shat on and raged about by people who probably couldn’t write a hello world app in any programming language. They’re just parroting the idea that Linux is vibecoded now, but it isn’t, and if anything they should be heartened by the recent decision to raise the bar for kernel contributors. Instead, they’re pretending Linus and other contributors aren’t trustworthy at all, based solely on a desire to feel outrage. When people correct them on these lies they’re spreading, no one ever admits they are wrong and stops spreading it, they just don’t respond to comments like that and continue writing them elsewhere.
I take it you’re another outrage junkie who cannot help but tell everyone the kernel is vibecoded. Your feedback is only valuable in that it communicated that
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.
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.
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.
nothing to be nervous about, its literally software engineering and project management 101, programmer writes code reviewer catches bugs, nothing goes to production. this happens all the time, has happened in the linux kernel way before LLMs were a thing
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.
can you elaborate on the recent fiasco you mentioned? I totally missed the news on that
Linus admitted he uses LLMs sometimes, so now the most trustworthy developer in the history of computers is now being shat on and raged about by people who probably couldn’t write a hello world app in any programming language. They’re just parroting the idea that Linux is vibecoded now, but it isn’t, and if anything they should be heartened by the recent decision to raise the bar for kernel contributors. Instead, they’re pretending Linus and other contributors aren’t trustworthy at all, based solely on a desire to feel outrage. When people correct them on these lies they’re spreading, no one ever admits they are wrong and stops spreading it, they just don’t respond to comments like that and continue writing them elsewhere.
Tldr; people are stupid.
You didn’t answer the question at all.
I take it you’re another outrage junkie who cannot help but tell everyone the kernel is vibecoded. Your feedback is only valuable in that it communicated that
Completely incorrect.
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
Race conditions are not unusual, and it was caught during review, so there’s really no problem here.
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.
I could attribute the race condition just as much to their use of the C language as to AI.
Race conditions I’m pretty sure aren’t language specific. Rust can have them too.
Yes, but the tools provided by Rust:
unsafe {}block to be used.Yea he basically said “This seems to work but is slop, lead Dev, make it real.”
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.
Great
This doesn’t make me nervous at all…
nothing to be nervous about, its literally software engineering and project management 101, programmer writes code reviewer catches bugs, nothing goes to production. this happens all the time, has happened in the linux kernel way before LLMs were a thing
It shouldn’t, because it’s a lie.
:/
This is why dictionaries list more than 1 definition and you shouldn’t stop at the first one:
https://www.dictionary.com/browse/lame
People who write this dictionary should listen to the public more maybe. Lame doesn’t mean what you wrote for at least 25 years.
Not what happened. I’m not digging it up but this story has been debunked repeatedly
(you’re welcome to just point folks to a debunking)
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.
Literally you got hit with an linux mailing list saying this is what happened?
Those words don’t make sense