You’re correct but still completely missing the point.
The only way to implement anti-LLM rules is to detect AI-assisted code. That, in and of itself, is a problem because it’s impossible to detect good code that was AI assisted. And you don’t need rules against slop because it’s bad code.
If I’m following it correctly, Linus is advocating for tightening submission requirements before it gets to human review, which directly targets the harms FOSS projects are having under the deluge of slop: it raises the bar so that the slop needs to be good enough to warrant a review, which filters out must of the noise, leaving more of the signal.
Anti-LLM policies are like having closed-book take-home exams: you’re left wildly guessing what’s cheating (or not). Instead, make the exam open book, but expect better answers.
Linus also says AI is a useful tool, and he is an expert, so we must accept that he feels that way. I don’t know if he’s commented on the environmental/social/political consequences of AI hyperscalers, but that’s a separate argument.
The tech is here. It’s impossible to detect. It’s foolish to think you can ban it’s use
And it can be run locally, so there’s no stopping it, even if there was political will to do so. (And with a reasonable economic and ecological cost, no less—ignoring IP/political consequences here, since that’s a whole other topic.)
You’re correct but still completely missing the point.
Thanks ;)
The only way to implement anti-LLM rules is to detect AI-assisted code.
From direct experience, this just isn’t true. I contribute to a small open source project, and we’re doing well enough for our purposes by simply saying “no AI”. We’re not checking, we work on good faith. That’s enough for us. We have no reason to think people are circumventing it.
You’re correct but still completely missing the point.
The only way to implement anti-LLM rules is to detect AI-assisted code. That, in and of itself, is a problem because it’s impossible to detect good code that was AI assisted. And you don’t need rules against slop because it’s bad code.
If I’m following it correctly, Linus is advocating for tightening submission requirements before it gets to human review, which directly targets the harms FOSS projects are having under the deluge of slop: it raises the bar so that the slop needs to be good enough to warrant a review, which filters out must of the noise, leaving more of the signal.
Anti-LLM policies are like having closed-book take-home exams: you’re left wildly guessing what’s cheating (or not). Instead, make the exam open book, but expect better answers.
Linus also says AI is a useful tool, and he is an expert, so we must accept that he feels that way. I don’t know if he’s commented on the environmental/social/political consequences of AI hyperscalers, but that’s a separate argument.
The tech is here. It’s impossible to detect. It’s foolish to think you can ban it’s use
And it can be run locally, so there’s no stopping it, even if there was political will to do so. (And with a reasonable economic and ecological cost, no less—ignoring IP/political consequences here, since that’s a whole other topic.)
Thanks ;)
From direct experience, this just isn’t true. I contribute to a small open source project, and we’re doing well enough for our purposes by simply saying “no AI”. We’re not checking, we work on good faith. That’s enough for us. We have no reason to think people are circumventing it.