They got to him

  • 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
      ·
      7 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
        ·
        26 minutes ago

        the anti-AI circlejerk

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