• tumbling4986@lemmy.caOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 hour ago

      Even linux kernel, debian allows responsible AI commits 😅 Then why not flathub. Right? 😂

  • Dalaryous@lemmy.world
    link
    fedilink
    English
    arrow-up
    15
    arrow-down
    6
    ·
    11 hours ago

    Makes sense. AI can accelerate experienced coders. I’m ok to see people use AI for helping but NOT for Vibe Coding.

      • ImgurRefugee114@reddthat.com
        link
        fedilink
        English
        arrow-up
        8
        arrow-down
        1
        ·
        edit-2
        5 hours ago

        I can only talk from personal experience, but it absolutely does speed up things. I know because I went from working away at one project to progressing many projects at the same time. Starting up new projects I never would have bothered to do in the first place just because the work would have been so tedious and I wouldn’t have enough time in the day. Mind you, I don’t vibe code things for public consumption. These are all for my personal use, but the fact that they exist at all is evidence contrary to your points.

        (Important note: how I use AI in important software is very different from how I use AI for slop projects; the speedups are not as dramatic when you aren’t vibrcoding and you actually need good quality; I suspect most AI usage would actually be a slight downgrade for speed unless I delegated them strictly to review and menial implementation; but that actually assumes that I know the language I’m working in very well, which isn’t always the case for vibecoded projects: In those cases, the AI slop is probably equal to or better than what I would write by hand because I’m not as competent in elixir or javascript as I am in C or C++)

        I feel like this is dishwasher discourse… Washing by hand is faster than the dishwasher by the wallclock; but you don’t actually need to rinse as much as you probably do, and you can walk away and do other stuff while the dishwasher is working. If you just sit there and stare at the dishwasher, yes, it’s slower, but that’s not how people should use it, and that’s what most of those studies are showing. Again, that level of sloppiness isn’t applicable for all use cases, but for where it is useful, it is very useful.

    • just_an_average_joe@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      12
      arrow-down
      4
      ·
      11 hours ago

      That’s like saying social media can make people more social, when we know that for most people it just leads to addiction.

      Human brains are designed to find shortcuts, vibe coding is one of them. I’ve seen plenty of senior devs fall into this trap.

        • FaceDeer@fedia.io
          link
          fedilink
          arrow-up
          11
          arrow-down
          4
          ·
          13 hours ago

          Doesn’t it? Trying to ban sunlight in the desert means you will waste a ton of resources, fail, and look foolish in the process. Maybe you shouldn’t do that.

              • zod000@lemmy.dbzer0.com
                link
                fedilink
                English
                arrow-up
                5
                arrow-down
                1
                ·
                5 hours ago

                It was a poor metaphor. You absolutely can ban AI software in software you control. If someone then managed to lie and sneak some in and gets found out, ban them and purge their contributions.

        • inari@piefed.zip
          link
          fedilink
          English
          arrow-up
          12
          arrow-down
          3
          ·
          14 hours ago

          Maintainers are busy enough as is without having to take on the additional role of AI police

        • fonix232@fedia.io
          link
          fedilink
          arrow-up
          3
          arrow-down
          2
          ·
          11 hours ago

          Open source maintainers have enough trouble without trying to ban all AI generated code just to comply with a distributor.

          AI code is inevitable. Even if you outright ban it, people will try to sneak it in. Lets say the change is literally just changing the order of calls to fix a bug - but the person who found and fixed the bug used AI to do so. Do you ban that? If it’s not disclosed, how would you know? After all the commit is literally just a line order swap. What if the committer actually hand wrote that fix but used AI for the PR body because they don’t speak English well and don’t want to appear dumb?

          The best practice is to allow AI-generated code as long as the person providing the commit can properly reason about its function - meaning they understand what the code does and have done their due diligence. Good quality AI generated code isn’t the issue, it’s the skiddies who think prompting Claude with the most basic queries and blindly accepting the output until the one thing they wanted to achieve works, results in usable code. It results in unmaintainable slop. You need an actual engineer with experience to review it, but maintainers don’t have that capacity, so banning slop and requiring contributors to understand what they’re trying to get merged is the best way forward.

          • FartMaster69@lemmy.dbzer0.com
            link
            fedilink
            English
            arrow-up
            3
            arrow-down
            1
            ·
            11 hours ago

            There are serious legal concerns about what integration of AI code could mean for open source licenses as it’s already been decided that AI generated content cannot be copyrighted.