Linux Kernel Becoming a Slopfest - Part 8 - In Conclusion
In Part 1, Part 2, Part 3, Part 4, Part 5, Part 6, and Part 7 we showed that the plagiarism frenzy (I have my own take on what it is and what will happen to it) has infected or contaminated Linux. This is sad; we also showed some of the worst culprits, including the top one; this man being a Microsofter was "not a surprise" to an associate; "a disappointment but not a surprise..."
In IRC, in the meantime, a regular spoke of "Microsofters' "therapy" of [Linus] Torvalds," saying that it "paid off, [as] he himself is now turning back against freedom and more e-waste now..."
He is also tolerating slop and acts as if the real problem is people who 1) insist on people writing and auditing code; 2) oppose plagiarism.
In a previous part we explained this can invite more SCO-like problems in the future.
What began as an excellent (even RMS commended it on occasions) kernel is fast becoming a shebang of LLM slop.
This won't end well.
"We have a copy of Linux's git archive on the devel system now," an associate had told me. We initially had it on the production system and "[i]t took over 70 minutes to rsync from there."
On a fast connection it takes over an hour just to pass the code (or history thereof) of today's bloated Linux.
We've cleared up the space on the server (8.3GB), now we can more closely study what else (e.g. tagged-as-LLM/slop 'code') the repo tells us. Remember that a lot of slop isn't properly flagged ("tagged") by committers, so we cannot see the full breadth of the problem. █