• ghost_laptop@lemmy.ml
    link
    fedilink
    arrow-up
    68
    arrow-down
    13
    ·
    7 days ago

    jesus christ… it’s been said over a million times, the development of the linux kernel is not some fucking 5 star github repo. it goes through a shit ton of review, it’s seen by a lot of eyes. a small piece of text that says it was assisted or not by ai is irrelevant if the code is good or not, which is the work of maintainers to decide.

    • atomicbocks@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      22
      arrow-down
      5
      ·
      6 days ago

      On the contrary, a small piece of text that says “this code deserves more review because humans may not have seen it” is absolutely necessary.

      All this is doing is making it so I can hide that I didn’t touch the code.

      • alottafagina@lemmy.ml
        link
        fedilink
        arrow-up
        11
        arrow-down
        8
        ·
        6 days ago

        On the contrary, a small piece of text that says “this code deserves more review because humans may not have seen it” is absolutely necessary.

        All this is doing is making it so I can hide that I didn’t touch the code.

        Why are you assuming that everyone would honestly disclose AI use if it was a rule?

        The honest ones that would disclose it to say “this needs more eyes, guys” can still do just that. The dishonest ones that would hide AI use will do exactly that whether it’s a rule or not.

        The only difference here is there’s no punitive action to follow for non-disclosure because that would be a gigantic waste of time when, AI or not, all code needs to be reviewed anyway.

        • atomicbocks@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          14
          arrow-down
          3
          ·
          6 days ago

          I have to say the same thing I said to the other commenter; I’m really not sure that “some people lie so nobody should care about the truth” is the argument you think it is.

          • alottafagina@lemmy.ml
            link
            fedilink
            arrow-up
            4
            arrow-down
            16
            ·
            6 days ago

            I have to say the same thing I said to the other commenter; I’m really not sure that “some people lie so nobody should care about the truth” is the argument you think it is.

            Nice attempt at spin but relies too much on readers having room temperature IQ to believe that’s what my argument is. And just to be clear, by ‘Nice attempt’ I’m being sarcastic.

      • Auli@lemmy.ca
        link
        fedilink
        English
        arrow-up
        2
        arrow-down
        2
        ·
        5 days ago

        So then the person who doesn’t put that in, doesn’t get reviewed. Are you dumb enough to think everyone well follow the rules?

        • atomicbocks@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          2
          ·
          5 days ago

          For the third time; “some people lie so nobody should care about the truth” is not the argument you think it is.

      • ghost_laptop@lemmy.ml
        link
        fedilink
        arrow-up
        3
        arrow-down
        7
        ·
        6 days ago

        because there is no guarantee the code will be wrong per se. should junior developers need to disclose this fact, then? because according to your logic their code could be wrong! furthermore, there’s the fact people will do whatever the fuck they want, regardless of you raging on an internet forum about disclosure. people might not even read that shit because they don’t give a fuck. so you end up with half assed policy which you cannot enforce. job well done, let’s go home boys.

        • atomicbocks@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          7
          arrow-down
          1
          ·
          6 days ago

          Junior developers’ code always goes through more review, yes. Also, I’m not sure “some people lie so nobody should care about the truth” is the argument you think it is.

          • ghost_laptop@lemmy.ml
            link
            fedilink
            arrow-up
            5
            arrow-down
            5
            ·
            6 days ago

            no, people who have never contributed to the linux kernel are “flagged” simply because maintainers have never seen this person, but there’s no “junior developer disclosure policy”. you could be a senior dev who simply is contributing for their first time. you could be receiving ai assisted code by very old contributors, for example, which in the eyes of the maintainers is a certain feeling of trust precisely because that person has a history with the project. i think your comprehension skills are poor, since that’s not what i said. my argument is that a policy that cannot be enforced and as argumented also provide very little gain, is not doing much at all. if a policy does nothing, what is the purpose of this policy?

            • Auli@lemmy.ca
              link
              fedilink
              English
              arrow-up
              2
              arrow-down
              1
              ·
              5 days ago

              In their eyes it does something though it gives them something to rage about.

      • alottafagina@lemmy.ml
        link
        fedilink
        arrow-up
        19
        arrow-down
        3
        ·
        6 days ago

        Because rules have to be enforced, and investing time and effort into detecting and punishing rule-breakers would be a pointless endeavor when, disclosure/AI or not, all code has to be reviewed anyway.

      • geneva_convenience@lemmy.ml
        link
        fedilink
        arrow-up
        12
        arrow-down
        2
        ·
        6 days ago

        According to Linus it’s free advertising for the AI companies (wowe look at how much code Claude (partially) committed buy le Anthropic now!) and also people don’t disclose all their other tools either so this is just an exception which can be removed. And I bet there’s going to be a ton of LLM based reviewing on all code that’s submitted to double check for potential bugs anyway.

        Anyone who is allowed to work in the Linux kernel isn’t going to (be allowed to) push random slop.

      • ghost_laptop@lemmy.ml
        link
        fedilink
        arrow-up
        4
        arrow-down
        1
        ·
        6 days ago

        maybe we should ask the maintainers, since it’s they’re the ones where this disclaimer could be useful or not. :)

    • chloroken@lemmy.ml
      link
      fedilink
      English
      arrow-up
      9
      arrow-down
      4
      ·
      6 days ago

      It’s been said a billion times: you don’t get to decide what I find relevant. The only reason these clowns want to hide their behavior is because they’re ashamed of the criticism. There is no other reason to hide attribution, your patronization notwithstanding.

      • ghost_laptop@lemmy.ml
        link
        fedilink
        arrow-up
        4
        arrow-down
        2
        ·
        6 days ago

        the developers of the linux kernel, people who have probably been coding for at least 20 years, are clowns.

      • CheesyFox@lemmy.sdf.org
        link
        fedilink
        arrow-up
        3
        arrow-down
        2
        ·
        6 days ago

        by that logic, devs should also disclose their preferred IDE, colorscheme, and favorite programming language. Mine are kakoune, gruber dark(-ish custom) and rust respectively btw. I’m not ready to trust someone with python in their favorites (I’m extremely racist towards python)

    • Phoenixz@lemmy.ca
      link
      fedilink
      arrow-up
      5
      arrow-down
      6
      ·
      6 days ago

      Completely this.

      As long as the code is good,. does it matter where it came from?

      • chloroken@lemmy.ml
        link
        fedilink
        English
        arrow-up
        6
        arrow-down
        4
        ·
        6 days ago

        Yes, fuckstick. That’s the whole point to a lot of people.

        I swear, the level of smugness of AI true believers is totally inappropriate.

        • ghost_laptop@lemmy.ml
          link
          fedilink
          arrow-up
          4
          arrow-down
          3
          ·
          6 days ago

          we’ll be waiting in the grown ups room while you figure out how to answer the question “why?”

    • Ooops@feddit.org
      link
      fedilink
      arrow-up
      5
      arrow-down
      6
      ·
      edit-2
      6 days ago

      But that doesn’t matter! Join the crusade!! AI is either the devil incarnate or our lord and savior! No in-between (no sanity in particular) allowed.

      And as long as you have still not gone insane and argue rationally the bombardment of at least one pro-, one anti-AI post/article about Linux per day has to continue…

      • ghost_laptop@lemmy.ml
        link
        fedilink
        arrow-up
        3
        ·
        6 days ago

        i feel you, i honestly been feeling the need to avoid the linux community (although i’ve obviously failed) for some time because is tiring.

        • alottafagina@lemmy.ml
          link
          fedilink
          arrow-up
          2
          ·
          5 days ago

          tiring

          Hate to tell you this but that’s probably a core feature here.

          Someone was trying to argue here that code is less about what it actually does and more about the feelings that drove them (as distinct from thought processes or motivating logic behind them) and since AI betrays this, must AI disclosure blah blah!!!

          Once arguments have entered the realm of absurdity and legitimate discourse is overshadowed by bad faith discussions of shifting goalposts and gish gallops, the only question that remains is who stands to gain the most from the english speaking world being slow to adopt AI.

          Once reasonable heads have left the room and decline to discuss any topic on AI (because they expect the toxic environment devoid of reason), only agenda driven collectives and a handful of their useful idiots will steer future discourse.

  • Artemis_Mystique@lemmy.ml
    link
    fedilink
    arrow-up
    13
    arrow-down
    3
    ·
    6 days ago

    As some one here summarised it: it is to stop AI companies from getting free advertisement and endorsement, the kernel itself goes through an unbelievable amount of scrutiny so the disclosure requirement was irrelevant

  • nonentity@sh.itjust.works
    link
    fedilink
    arrow-up
    10
    arrow-down
    2
    ·
    5 days ago

    If the use and inclusion of LLM derived output is truly defensible, why would you need to conceal its provenance or existence?

    The debasement and solvency of competency wrought by the unbridled abdication to responsibility to such an incompetent construct is beyond depressing, this Is truly a world no longer worth inhabiting.

    • ☆ Yσɠƚԋσʂ ☆@lemmy.ml
      link
      fedilink
      arrow-up
      5
      arrow-down
      2
      ·
      5 days ago

      The question is why it matters in the first place. As long as the person submitting code takes ownership of the code, and there is a review of the code being done the same as before, nothing actually changes. Your whole line of argument is absurd because it’s premised on the idea that we can trust code produced by a human more than code produced by an LLM. And that’s obviously not true because humans make mistakes all the time. So, the focus on how the code was produced is fundamentally misguided. The focus in any successful project is on validation through things like code reviews, specifications, testing, and other well established practices. That’s what responsible teams have always done.

      • nonentity@sh.itjust.works
        link
        fedilink
        arrow-up
        3
        arrow-down
        2
        ·
        5 days ago

        To me, it matters because the use and reliance on LLMs demonstrably erodes cognitive capacity and ability, and submissions tainted by them should be subjected to an elevated level of scrutiny, which can only be facilitated with a consummate element of transparency. That elevated scrutiny could, and probably should, also be applied to non-LLM infected submissions, but doing so wouldn’t negate the labelling of authorship.

        Good faith proponents of LLM assisted tooling should be in favour of overt transparency and labelling, as it’s a requirement to facilitate future historical analysis of their utility, efficacy, and legitimacy; you know, to build a body of evidence.

        • ☆ Yσɠƚԋσʂ ☆@lemmy.ml
          link
          fedilink
          arrow-up
          4
          arrow-down
          2
          ·
          5 days ago

          I assume you’re citing a couple of studies with tiny samples that have been going around here. There’s very little solid evidence to support the claim that LLMs demonstrably erode cognitive capacity. But if you have large scale, peer reviewed studies definitively showing this to be the case feel free to share them.

          People lose certain skills working with LLMs, but that has always been the case with automation. Very few people know how to write assembly by hand, and practically nobody knows how to operate punch cards. Yet, we hardly claim that there was some loss of cognitive capacity as a result. People just spend their time focusing on different things now.

          And I’ve already explained to you why the focus on the tooling is deeply misguided. You ignored my points entirely, which tells me that you’re not actually trying to have a discussion in good faith here yourself.

      • ormith@lemmy.world
        link
        fedilink
        arrow-up
        2
        arrow-down
        2
        ·
        5 days ago

        To me it matters because if you got code from someone else, you’d probably want to credit it to them, right? So why shouldn’t LLM output be treated the same?

            • ☆ Yσɠƚԋσʂ ☆@lemmy.ml
              link
              fedilink
              arrow-up
              2
              arrow-down
              2
              ·
              4 days ago

              The LLM works on the exact same principle as autocomplete does. You’re just drawing an arbitrary line on technology you’re used to.

              • ormith@lemmy.world
                link
                fedilink
                arrow-up
                1
                ·
                4 days ago

                True in some regards, however the word completion in my IDE is only active when I’m typing new code in, it only picks words that already exist in the code (along with language specific keywords, etc). It never types the following word for me, and I have to manually accept the completion I want. It is inactive when I’m typing comments in, and so on.

                The LLM you tell to write you a function, and it writes the whole thing, comments and all. It’s not quite the same. The original GitHub Copilot was closest to traditional IDE completion though, and there if it wrote a whole long function for me I’d definitely give credit where it’s due.

                • ☆ Yσɠƚԋσʂ ☆@lemmy.ml
                  link
                  fedilink
                  arrow-up
                  2
                  arrow-down
                  1
                  ·
                  4 days ago

                  It’s a different workflow, but all LLM does is just more automation. The intention and the ideas still come from the developer, just because the tool automates the work of typing out code doesn’t really change anything. Nobody who’s done any serious software development thinks that typing code is the important part of coding.

              • nonentity@sh.itjust.works
                link
                fedilink
                arrow-up
                1
                arrow-down
                1
                ·
                4 days ago

                Anyone who believes, and confidently espouses, that the autocomplete from the dictionary included in an IDE is functionally indistinguishable from the function and output of a LLM, is betraying a foundational lack of understanding of either. The former is constrained and deterministic, whereas the latter is explosively imprecise and intrinsically unreliable.

                You keep invoking the notion that LLMs are merely tools, and should be treated as mindless subservient instruments deployed by a programmer in command. The thing, however, with tools is they can often trivially become weapons if wielded with incendiary intent, or indiscriminate instruments of destruction under the direction of incompetence.

                Skill is acquired through use over time. LLMs are far too new for anyone to have legitimately accrued enough experience which could be mistaken for competence. With this in mind, anyone claiming to know what they, or the model they’re poking with a prompt, are doing, is a charlatan.

                • ☆ Yσɠƚԋσʂ ☆@lemmy.ml
                  link
                  fedilink
                  arrow-up
                  2
                  arrow-down
                  2
                  ·
                  4 days ago

                  Anyone who makes lazy straw man arguments is betraying utter lack of intellectual integrity. Nowhere did I say their output is indistinguishable, what I actually said is that they work on the same principles. These are both stochastic systems.

                  The LLMs are very obviously mere tools that are instruments programmers use. Every tool can be wielded as a weapon, there’s nothing unique about LLMs in this regard. I also have no idea what this has to do with AI use disclosure which is the context for this thread.

                  How LLMs work is well understood, and that’s a completely different subject from how to use them effectively as a skill. With this in mind, the person who can’t even make a coherent argument, and keeps conflating unrelated things, is the actual charlatan here.

    • iglou@programming.dev
      link
      fedilink
      arrow-up
      3
      arrow-down
      2
      ·
      5 days ago

      Who said anything about concealing it? Not making adisclaimer mandatory and concealing something are two different things.

      From the point of view of a reviewer, the code of the PR is all that matters. You shouldn’t look at who wrote the code or what tools they used.

      If the code is slop, it does not matter that a human or an AI wrote it, it is slop. Same if the code does what it’s supposed to do and has a high enough quality to pass review.

  • blackshirt@lemmy.world
    link
    fedilink
    arrow-up
    7
    arrow-down
    2
    ·
    6 days ago

    I guess, as he suggested, it’s time to fork it.

    the hardest part is to come pu with a good project name and mascot.

  • VOIDPTR@lemmy.ml
    link
    fedilink
    arrow-up
    4
    ·
    6 days ago

    It would be interesting if this results in Linux being forked or perhaps even more interesting developers and users opposed to AI moving to GNU Hurd or any of the BSD variants.

    • ghost_laptop@lemmy.ml
      link
      fedilink
      arrow-up
      1
      arrow-down
      1
      ·
      5 days ago

      good luck with that. software development has changed and it will never be the same. you will not be able to achieve the level of security required without ai assistance, you can’t beat a machine. and this is something you’ll see everywhere and is the tip of exponential curve.