Elektrine lite

← Feed

@thingsiplay@lemmy.ml

2026-10-16 22:27 UTC

I agree with you that the Kernel isn’t doing slop. But there are a few points I want to address, maybe even disagree. First let me say that people have different definition of what slop means. That is why we don’t always agree on statements involving slop. he Kernel actually has a huge number of maintainers. True, but its still not enough to handle all slop. One problem is, its not always apparent at first glance. And more code is generated than ever before, surpassing the capabilities, time and nerves of all maintainers. That means they start using Ai to combat the amount. And that’s an issue on itself. Writing bad code isn’t something new, and isn’t unique to LLM’s. Coders (and it seems some “journalists”) have been writing slop since computers were invented. This might be true, but that is not a reason to accept or normalize slop. It does not matter how much slop was before, we always try to minimize it. The difference to before is, that nowadays its easier and faster to write (or generate) slop in mass that looks legit. Finding out its bad code or wrong can suck up huge amount of time of maintainers, which would have worked on something more productive instead. The only thing that matters is the human who submitted the code For you maybe, but there are issues using Ai regardless of how the code looks. And I don’t even talk about the amount of code it can generate and outpace every maintainer capacity. I mean stuff like how the LLM was trained on in example, and if the licensing will become an issue one day. While the Linux Kernel operates very securely and in a controlled manner, that we cannot call it slop (yet). But there are inherent problems using Ai that are unsolved.

Replies (4)

  • @Cris_Citrus@piefed.zip 2026-10-16 22:56

    Well put, thank you :)

    Open ##5071196

  • @auzy1@lemmy.world 2026-10-16 23:06

    True, but its still not enough to handle all slop. The number of maintainers have also grown though dramatically… Also, don’t forget that LLM’s can also be used to identify bugs in patches more quickly too… So, more are getting submitted, but, lots of bad patches are being rejected faster too, with less effort (that required human intervention in the past). This might be true, but that is not a reason to accept or normalize slop. Define Slop… The difference to before is, that nowadays its easier and faster to write (or generate) slop in mass that looks legit. Finding out its bad code or wrong can suck up huge amount of time of maintainers, which would have worked on something more productive instead. We’ve all spent hours doing that though on our own code. Again, the buck stops with maintainers. One thing that Maintainers are going to do though, is get them to prove the code first and test the code in other trees first, before even trying to push to main There’s always been code that has been bad, like Linus never liked the Con Kalivas performance patches, or Reiser4. It is also finding a lot of security issues and bugs faster too though I’ve actually written optimisations for code that I thought would be faster, and turned out to be a waste of time in production For you maybe, but there are issues using Ai regardless of how the code looks. Both sets of code need the same level of examination by humans anyway. In fact, in some cases, the AI code I’ve seen has been better than the code i wrote I mean stuff like how the LLM was trained on in example, and if the licensing will become an issue one day. That is true, and I agree with that. That’s the one point that does stand out, but doesn’t have anything to do with the claim by certain people in the community about the Linux Kernel being overrun with bad code. What I would like to see is a LLM that’s developed exclusively using Open source compatibility licences with FULL traceability to sources uses, and a way to specify licencing allowed (or something similar). There is one issue with AI that you didn’t mention however. The biggest problem with AI is that it adversely benefits closed source companies via Open source code. Because closed source code isn’t easily accessed by the AI for training, but Open source is. The other issue is that hackers won’t avoid LLM’s based on the ethical issues, so, unfortunately, it forces developers to use them to keep up with the cat and mouse game. As a developer, am I happy about AI? For code review yes, but, it makes my job suck and not fun. And no, I’m not happy about the ethics… There are a lot of things that sh** me, like AI companies SHOULD be forced to pay royalties to everyone they stole info from. However, what sucks, is that we can’t pretend it’s not a thing, and if Linux wants to remain competitive, it does need to use it. The best thing we can do though, is petition to tax AI companies and pay producers of the information. That would make AI unprofitable immediately and kill the industry

    Open ##5071388

  • @atzanteol@sh.itjust.works 2026-10-17 12:43

    It does not matter how much slop was before, we always try to minimize it. There is no policy that will stop that. It’s happening whether you want it to or not. What every project needs is a way to handle submissions that ensures a level of quality. The kernel has this. Also needing to police whether code was llm generated would be an increased burden.

    Open ##5081984

  • @glibg10b@lemmy.zip 2026-10-18 04:34

    All of what you said is true applies to any open source project. They’re all being flooded with slop PRs. But I would argue that the Linux kernel handles this in one of the best ways that they currently can. Wouldn’t you be inclined to agree?

    Open ##5098514