The GNOME.org Extensions hosting for GNOME Shell extensions will no longer accept new contributions with AI-generated code. A new rule has been added to their review guidelines to forbid AI-generated code.

Due to the growing number of GNOME Shell extensions looking to appear on extensions.gnome.org that were generated using AI, it’s now prohibited. The new rule in their guidelines note that AI-generated code will be explicitly rejected

  • theneverfox@pawb.social
    link
    fedilink
    English
    arrow-up
    16
    ·
    10 hours ago

    The difference is people aren’t being responsible with AI

    You’re projecting competence onto others. You speak like you’re using AI responsibly

    I use AI when it makes things easier. All the time. I bet you do too. Many people are using AI without a steady hand, without the intellectual strength to use it properly in a controlled manner

    • Hawk@lemmynsfw.com
      link
      fedilink
      arrow-up
      3
      ·
      10 hours ago

      Its like a gas can over a match. Great for starting a campfire. Excellent for starting a wildfire.

      Learning the basics and developing a workflow with VC is the answer.

        • Hawk@lemmynsfw.com
          link
          fedilink
          arrow-up
          4
          ·
          9 hours ago

          Large language models are incredibly useful for replicating patterns.

          They’re pretty hit and miss with writing code, but once I have a pattern that can’t easily be abstracted, I use it all the time and simply review the commit.

          Or a quick proof of concept to ensure a higher level idea can work. They’re great for that too.

          It is very annoying though when I have people submit me code that is all AI and incredibly incorrect.

          Its just another tool on my belt. Its not going anywhere so the real trick is figuring out when to use it and why and when not to use it.

          To be clear VC was version control. I should have been more clear.

          • theneverfox@pawb.social
            link
            fedilink
            English
            arrow-up
            3
            ·
            9 hours ago

            Okay, that’s pretty fair. You seem to understand the tool properly

            I’d argue that version control is not the correct layer to evaluate output, but it is a tool that can be used in many different ways…I don’t think that’s a great workflow, but I can conceive situations where that’s viable enough

            If I were handing out authorizations to use AI, you’d get it

    • uncouple9831@lemmy.zip
      link
      fedilink
      arrow-up
      1
      ·
      9 hours ago

      Banning a tool because the people using it don’t check their work seems shortsighted. Ban the poor users, not the tool.

      • theneverfox@pawb.social
        link
        fedilink
        English
        arrow-up
        5
        ·
        9 hours ago

        We do this all the time. I’m certified for a whole bunch of heavy machinery, if I were worse people would’ve died

        And even then, I’ve nearly killed someone. I haven’t, but on a couple occasions I’ve come way too close

        It’s good that I went through training. Sometimes, it’s better to restrict who is able to use powerful tools

        • uncouple9831@lemmy.zip
          link
          fedilink
          arrow-up
          2
          ·
          edit-2
          6 hours ago

          Yeah something tells me operating heavy machinery is different from uploading an extension for a desktop environment. This isn’t building medical devices, this isn’t some misra compliance thing, this is a widget. Come on, man, you have to know the comparison is insane.