Direct link to the LLM Policy Discussion: https://invent.kde.org/plasma/plasma-workspace/-/work_items/187

Example of a KDE dev not wanting environmental concerns to play any role, despite KDE having an environmental project:

Devs rejecting any notion of transparency by disclosing AI usage in code submissions (in direct opposition to advice from the FSFE):

And all of this is coming right after the debacle with an AI slop project being allowed to give a presentation at Akademy, and the person asking how this was allowed being blocked by KDE:

https://lemmy.nz/post/42029517

as well as the discussion thread bringing up legitimate concerns about AI usage being closed:

https://discuss.kde.org/t/sorry-to-bring-up-a-contentious-topic-kde-ai-llm-policy/46333/164

As someone who genuinely loves KDE, and has even donated to the project multiple times, I sadly have to accept that the majority of KDE have hopped onto the Pro-AI train, and they will not be dissuaded otherwise.

  • AceFuzzLord@lemmy.zip
    link
    fedilink
    arrow-up
    33
    arrow-down
    2
    ·
    20 hours ago

    It starts with “oh, just clean up any code generated” and “you must understand what your code does” and then in a decade that person won’t remember how to code at all because they self-lobotomized themselves for the convenience.

    • Sina@beehaw.org
      link
      fedilink
      arrow-up
      4
      arrow-down
      1
      ·
      7 hours ago

      I don’t think becoming a worse coder is necessarily a big problem as long as code review really happens, as long as the human in the picture retains their algorithmic thinking there is no lobotomy. Of course we all know how human laziness works, so thinking that people would actually keep reviewing code after they find no major issues N times in a row is a pipe dream.

      And I don’t know about you guys, but I for one dislike reading someone else’s code. LLM generated blocks can be especially bad for testing my sanity.