• zr0@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    11
    arrow-down
    11
    ·
    1 day ago

    Have bigger problems than this. If the code is reviewed and tested, I don’t care if it was written by a human or machine. Sometimes I feel like people don’t trust recording audio on tapes and praise the good old punch cards.

    • spartanatreyu@programming.dev
      link
      fedilink
      arrow-up
      17
      arrow-down
      3
      ·
      1 day ago

      If the code is reviewed and tested, I don’t care if it was written by a human or machine.

      That’s a pretty big assumption there buddy.

      If they didn’t care enough to write the code, what makes you think they cared enough to review or test the code?

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

        If they didn’t care enough to write the code, what makes you think they cared enough to review or test the code?

        Contributors =/= Maintainers.

        • TootSweet@lemmy.worldM
          link
          fedilink
          English
          arrow-up
          11
          arrow-down
          5
          ·
          1 day ago

          If the maintainers didn’t care enough to summarily reject anything AI-generated out of hand, what makes you think they cared enough to review or test the code?

          • x1gma@lemmy.world
            link
            fedilink
            arrow-up
            3
            arrow-down
            1
            ·
            1 day ago

            You’re dropping assumptions, and nothing more. Why do you think they asked for disclosure of AI usage? People are gonna use it anyway, officially or not. They did this call for this so that it can be reviewed properly.

      • zr0@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        1
        arrow-down
        1
        ·
        1 day ago

        You’re way quicker manually reviewing code compared to setting up everything just so that an LLM agent could do that. Additionally, it is open source. Literally nothing gives you any guarantees that the software will work in the first place. If you are scared of that, commercial products are your choice.

        • spartanatreyu@programming.dev
          link
          fedilink
          arrow-up
          1
          ·
          edit-2
          8 hours ago

          You’re way quicker manually reviewing code compared to setting up everything just so that an LLM agent could do that.

          Not only that, you’re better off reviewing the code manually so you understand how everything works.

          If you understand how things work, you can plan things out.

          If you don’t, you’ll end up painting yourself into a corner.

          If you are scared of that, commercial products are your choice.

          Commercial products are not a panacea for bad software quality.

          Code openness and code quality are independent, orthogonal axes.

      • tangonov@lemmy.ca
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        14 hours ago

        Mostly because AI isn’t capable of doing a perfectly good job without humans at this point. Vim may have started using AI as part of the development toolchain so that tired people working in their free time for free can propel their own work. To me this was always going to happen whether it gets committed discreetly or not. I don’t think people will tolerate it if these commits hurt the long term, reputable stability of Vim.

        We can stop pretending that AI isn’t used discreetly in many and perhaps eventually all the projects that we love. Intolerance and toxic harping on open source is still the bigger problem