• ZILtoid1991@lemmy.world
    link
    fedilink
    arrow-up
    10
    arrow-down
    1
    ·
    1 day ago

    At least until the AI slop updates don’t reach the kernel (at least they’re banned from some parts of it).

    • Nalivai@lemmy.world
      link
      fedilink
      arrow-up
      7
      arrow-down
      4
      ·
      1 day ago

      Linus was openly not-anti-slop recently, so I don’t have enormous amount of hopes.

      • AstralPath@lemmy.ca
        link
        fedilink
        arrow-up
        7
        arrow-down
        1
        ·
        1 day ago

        How did you get that from what he’s said? Vibe coding is slop. Holding devs 100% accountable for their AI-assisted code is explicitly not allowing slop. He is doing the latter.

        • ZILtoid1991@lemmy.world
          link
          fedilink
          arrow-up
          1
          ·
          14 hours ago

          If “non-slop” AI art is anything to go by, then I don’t have much hope for it. I guess it will be “LGTM and it compiles”.

        • Nalivai@lemmy.world
          link
          fedilink
          arrow-up
          2
          arrow-down
          2
          ·
          23 hours ago

          I’m referring to the letter of his when he said that he’s not going to ban generated code, not gonna “wage a war” on it or whatever. It might sound like “devs are still accountable for the code they commit” and all is a good position, but like with a lot of the other shit, if you’re not explicitly ban 100% of it, you’re now in a position of arguing with bots about nonsense. You still can be tough and all, but you’re alone and the bots are numerous and nonsense is neverending.
          That’s what I mean not-anti-slop, and right now it looks like being all fence-sitting about this wouldn’t actually work. I predict that he’ll either will rethink the policy, or limit the amount of patches merged significantly, or lose his mind and will write a big rant and possibly does something stupid.