Linux kernel memory-management code reviewer steps down due to influx of AI slop patches — volume of submissions coupled with low manpower forces the step back
I think you missing the point: we don’t want slop - as in low quality code. It does not matter if it is an AI or a Human created slop.*
*: just considering the project side, not the enironmental, and ethical side.
The problem is not identifying AI slop, the problem is wasting an already limited time on a PR which seems legit until you deep dive and find that it is utterly terrible. And multiple it with a large number of PR-s because the barrier of entry to create a slop is 0.
I think you missing the point: we don’t want slop - as in low quality code. It does not matter if it is an AI or a Human created slop.*
*: just considering the project side, not the enironmental, and ethical side.
The problem is not identifying AI slop, the problem is wasting an already limited time on a PR which seems legit until you deep dive and find that it is utterly terrible. And multiple it with a large number of PR-s because the barrier of entry to create a slop is 0.