• o7___o7@awful.systems
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 month ago

    However, the approach here seems very sensible and the proof will continue to be in the pudding.

    The argument made by guys for abolishing food inspectors.

    • electric_nan@lemmy.ml
      link
      fedilink
      English
      arrow-up
      0
      ·
      1 month ago

      Give me a break. Look, I’ve been using Linux and FOSS tools for some time now (2007), but I dont code and I’ve never contributed any patches to any of the projects that I use. Who am I to tell unpaid volunteers what tools they use to make the software that I choose to use and enjoy? If doing a “first pass” with an AI tool helps take the load off these devs a little, without compromising the software* then good for them. If the software quality suffers, then I’ll use something else. Unlike with food safety standards, I have a choice whether or not to use this free, open source password manager.

      • e8d79@discuss.tchncs.deOP
        link
        fedilink
        English
        arrow-up
        0
        ·
        1 month ago

        The KeePassXC team just knowingly introduced a policy that is proven to produce vulnerable code into a software project where there is next to no margin for error and you are asking why we are upset? They can keep their vibe coded password manager.

        • electric_nan@lemmy.ml
          link
          fedilink
          English
          arrow-up
          0
          ·
          1 month ago

          You can be upset all you want to. I just think you’re overreacting based on what I’ve read.

              • self@awful.systems
                link
                fedilink
                English
                arrow-up
                0
                ·
                1 month ago

                oh no what happened to that thin veneer of reasonable centrism when you were defending a password manager of all fucking things incorporating slop code? could it be you just fucking love slop?