alt Hacker NewsPlease stop with the "AI assisted development" = "Vibe coding slop" narrative. It comes across as pretty dumb (sorry, I mean "uninformed") nowadays. Please experiment with LLMs, find your way (or don't, but), learn to talk about it in an informed way and don't post obviously inflammatory one liners that are essentially just "AI is bad m'kay".
There are intelligent arguments against using AI, your comment is not referring to any of them.
In short: Linus feels responsible for the quality of the Kernel, he expects the same of other devs. He does not care about the tools used to generate the code. He (or some other human) will call out submitted slop, whether LLM generated or human generated.
Replies
Making LLM write code is super susceptible to generating problems imo.
You know it won't be properly reviewed and understood.
Using LLMs to review code is much more useful imo but it can also cause problems due to the natural lazyness of a person.
You wouldn't want the OS you are using to be developed by a dilligent but a low IQ and mediocre skill level programmer.
I'm not saying other people can't possibly use LLMs to generate code effectively but it seems super suspicious from my experience as it triggers laziness and reluctance to put effort into understanding every piece of code.
It's increasingly the other way around, actually. You are being sloppy if you don't use the tools available to you. Including AI, static code analysis, testing tools, etc. to check if your work is any good. That doesn't mean you have to surrender to the AI tools and blindly generate everything and then commit without testing or any form of validation. That would be sloppy. But then if you manually write your code and did that, that would be sloppy too. Whether you manually type in all your code or have it generated is immaterial. What matters is the work you do to ensure it all works as advertised and is fit to be merged.
The kernel developers are probably a bit further in their thinking then some developers. They've been dealing with many thousands of contributors for decades. Git was invented by Linus Torvalds specifically to deal with ensuring only the best patches make it into the kernel.
Somebody posted a video with Greg Kroah-Hartman last week or so commenting on how he's been dealing with all the AI generated security bug reports. His key point is that AI generated reports are meaningless unless they come with a suggested fix as well. If you are going to generate the report, you might as well generate the fix. And it's a lot easier for him to review if the fix fixes anything worth fixing then to piece together a fix from a lengthy report. The larger the report, the less likely it is to get any attention. If the person contributing can't articulate why the fix is needed or how it works, they just reject the change and toss it back. That strikes me as very pragmatic. Judge a change on its merits. Not on how it was created. A report without a suggested fix is relatively meaningless.