They got to him

    • Buffalox@lemmy.world
      link
      fedilink
      English
      arrow-up
      33
      arrow-down
      4
      ·
      7 hours ago

      Maybe it did, but apparently the code was not properly reviewed initially, so there could be other hidden problems.
      Of course that’s the same for human made code, but there’s a problem in only judging code from how it performs, and not actually understanding the code. And that seems to be the situation with a lot of AI code.

      • db2@lemmy.world
        link
        fedilink
        English
        arrow-up
        17
        arrow-down
        1
        ·
        5 hours ago

        And particularly disturbing when the human understanding failure is from the original and lead Linux developer.

        • Buffalox@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          8 minutes ago

          100% that is the worst place to have the problem originate.
          I have rarely disagreed with Linus Torvalds, and maybe I’m wrong, but I strongly disagree with him on this issue. Contributing code nobody understands cannot be a good thing.

        • halcyoncmdr@piefed.social
          link
          fedilink
          English
          arrow-up
          6
          arrow-down
          3
          ·
          2 hours ago

          Is it an understanding failure, an unexpected interaction, or just an existing issue now exposed? A 23x performance increase could very well expose an existing race condition that systems weren’t fast enough to run into.

          People make mistakes. Software bugs existing at all is proof of this. This is certainly not the first time a change Torvalds approved has an issue, and it won’t be the last.

          There’s a reason code is reviewed, and there’s a reason people still go through after it is approved and verify. The process is working exactly as designed, the way it has for decades before AI coding.

          Expecting absolute perfection is ridiculous, the anti-AI circlejerk acting like only AI fucks up just makes them look ridiculous. Any developer could have developed this fix, and there would be no article. Nothing in this issue is specific to AI usage and treating it like it is somehow special just undermines arguments against AI slop and vibe coding in general.

          • db2@lemmy.world
            link
            fedilink
            English
            arrow-up
            1
            arrow-down
            1
            ·
            27 minutes ago

            the anti-AI circlejerk

            I’d say do better but that’s not likely to happen.

      • Diplomjodler@lemmy.world
        link
        fedilink
        English
        arrow-up
        3
        arrow-down
        5
        ·
        3 hours ago

        So, let me get this right. You’re disapproving on how things were handled based on your speculation of how it went?

        • Buffalox@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          13 minutes ago

          Not based on speculation, based on numerous analysis of the problems with using AI code you don’t understand.
          Clearly Linus failed to understand the code, otherwise he wouldn’t have suggested it for submission.

          You seem to have a problem with criticism of Linus, is it a religious thing?

    • devfuuu@lemmy.world
      link
      fedilink
      English
      arrow-up
      15
      arrow-down
      3
      ·
      5 hours ago

      Only while there are still reviewers who care to review the slop. Which is a rare breed and will quickly soon vanish.

      • corsicanguppy@lemmy.ca
        link
        fedilink
        English
        arrow-up
        1
        arrow-down
        1
        ·
        2 hours ago

        I bet some projects will get more tolerance and love than others, based on value and utility. The kernel will get more, and Systemd will get less.