80 points farlight 1 hour ago 35 comments
05kqhg 1 hour ago | parent
From the last paragraph:
"The Linux kernel is aimed at production use, not research or experimentation. But there is currently a massive experiment being run on the kernel's development processes and community."
mh- 46 minutes ago | parent
"This community has absorbed new processes and tools many times over its 35-year history, and will almost certainly find a way to do that this time as well. But that absorption has not always been without turbulence along the way."
Matl 1 hour ago | parent
It honestly doesn't want to make me open anything for outside contributions anymore.
mathisfun123 1 hour ago | parent
https://lore.kernel.org/lkml/CAHk-=whTs09_ozN+e09GU68N1wPP56...
senderista 59 minutes ago | parent
mathisfun123 55 minutes ago | parent
> Here's a new rule just for you: don't use compilers for any of your kernel submissions.
> Because if you can't show that you really understand what the machine is actually doing by writing your code in assembler, then I don't want to see your code contribution. You clearly aren't competent if you can't write it that way.
Matl 42 minutes ago | parent
mathisfun123 39 minutes ago | parent
sedan_baklazhan 6 minutes ago | parent
bitwize 17 minutes ago | parent
The point is, new technology arrived that allowed developers to do much more. Existing programmers hemmed and hawed about it because it threatened their egos, making easy what they once found very difficult. But the sensible engineers adopted the technology.
AI may not be deterministic, but on small to medium-sized tasks it produces more correct code, more reliably, faster than a human developer does. By any objective measure, not adopting it is professional irresponsibility.
cwillu 52 minutes ago | parent
vlovich123 50 minutes ago | parent
MobiusHorizons 23 minutes ago | parent
munchbunny 49 minutes ago | parent
> The kind of expectations I have is that people do their best and I expect people to understand what they are doing.
> But that understanding has very little to do with what tools they use.
> And quite honestly, in my experience, the people I respect and call intelligent are not the ones that shy away from using new and interesting tools.
He’s saying that understanding or competence are more about the person than their AI use. I think that’s a reasonable argument, even though I disagree on the basis that it’s at least a little correlated in the shortcuts in understanding the many devs I’ve seen (not all, but a nontrivial amount) seem to be taking.
senderista 23 minutes ago | parent
rvz 22 minutes ago | parent
He used Claude Code to write one of his patches in [0] and introduced a data race bug in the kernel unbeknownst to himself but this bug was caught by other reviewer [1] before it made it into a new kernel release.
So I'm afraid Linus himself did not understand the changes Claude made to the code he submitted in the mailing list, despite his "principles" in telling others previously that AI was creating slop patches and then now shouting at others who were concerned about using LLMs on code where they do not understand the generated code themselves when it all applied to....himself.
pelagicAustral 1 hour ago | parent
nvme0n1p1 1 hour ago | parent
nomel 1 hour ago | parent
Why? He seems very pragmatic. I fully expected him to embrace it, with the only concern being correctness and quality.
pelagicAustral 56 minutes ago | parent
bitwize 16 minutes ago | parent
The ones complaining about "slop" are the ones going on vibes now.
mycall 38 minutes ago | parent
teekert 16 minutes ago | parent
cwillu 1 hour ago | parent
(Edit: title has been fixed)
dang 55 minutes ago | parent
Submitters: If you want to say what you think is important about an article, that's fine, but do it by adding a comment to the thread. Then your view will be on a level playing field with everyone else's: https://hn.algolia.com/?dateRange=all&page=0&prefix=false&so...
lurk2 49 minutes ago | parent
ogoffart 54 minutes ago | parent
The agent helps a lot to fix bugs. Just point the agents at the bug reports. They do the reproduction, debugging and fixes. We "just" have to review. (Sometimes ask more details and tell we'd prefer another approach.) This makes bug fixing much faster and automated.
And at the same time, it seems we get less bug reports to our library. I think user just use their agents to code, and agents don't report bugs, they just work it around somehow.
So overall, the open bug count is decreasing. Which somehow feels good.
On the other hand, we get a lot of PR made by other's people agents, which can be a bit overwhelming when it's just a huge code drop. We can't easily review that.
fock 18 minutes ago | parent
timhh 7 minutes ago | parent
Yeah I've definitely noticed this. On a project I'm working on Opus 5.5 found a bug in Smithay and another in Winit. It did tell me about them but its preferred solution was just to work around them locally. To be fair we don't really want agents going off and reporting bugs automatically...
I don't run any big open source projects but I think my preferred solution to AI PRs would be to get my AI to implement the same thing, and give then afterwards tell it to look at the PR for anything it missed. Then I at least know that I'm using a competent model and it reduces the danger of just blindly accepting someone else's code. (And obviously review the code if you have time and care, but that isn't always the case.)
jayd16 52 minutes ago | parent
Historical numbers are not valid because incentivizes of a well funded entity have changed. It would require an equally well funded push to up the patch numbers without LLMs to really measure the impact in a quantifiable way.
zdw 41 minutes ago | parent
Which covers how he responds and pushes back on much of this, as well as asking for a patch (not just bug reports)
VCFundedGenYer 5 minutes ago | parent
New leadership is needed over there.