39

Timestamps:

00:00 Intro

00:36 Sponsor: TuxCare

01:46 KDE's AI policy

06:42 Existing AI policies

10:06 Going further on AI

12:58 My stance on AI

17:05 FOSS projects: yes or no to AI?

28:02 Sponsor: Tuxedo Computer

you are viewing a single comment's thread
view the rest of the comments
[-] CameronDev@programming.dev 3 points 21 hours ago

The KDE AI policy is pretty explicit about AI code contributions should have the same quality level as non-AI. So the tech debt concern is a nothing.

And there is no dependency risk, you can trivially switch from Claude to opencode w/ self hosted models, the AI companies have literally no moat to lock developers in. Its also entirely optional to use AI.

Environmental concerns are valid, but tech debt and dependency are silly arguments.

[-] naught101@lemmy.world 24 points 20 hours ago

I'm not talking about vendor lock-in, I'm talking about a system that has destroyed the training path for juniors, and the fact that as developers lean on AI more their skills atrophy and they become dependent on that workflow (regardless of provider), and their ability to introspect a code base decreases because they had less time learning it during the build-out phase.

[-] brucethemoose@lemmy.world 7 points 20 hours ago* (last edited 20 hours ago)

This was an issue in the computer science field well before LLMs, though (like in many areas) they did pour gas on the fire.

TBH I think it’s more of an issue for paid software. Manpower and burnout is the bottleneck for FOSS projects, and contributions are largely thankless, hence I think amongst the people who do contribute, there will be more of an interest in truly learning the codebase.

[-] naught101@lemmy.world 7 points 13 hours ago

Multiple FOSS projects have been complaining over the last year or so that they are getting swamped with LLM-generate PRs that are often low-quality, but still require a similar amount of time to review. LLMs are shifting extremely lited FOSS core maintainer capacity away from development and into time-wasting code reviews with a high rejection rate.

[-] brucethemoose@lemmy.world 2 points 6 hours ago* (last edited 6 hours ago)

Well, yes, and that’s exactly what the KDE policy is addressing. They’re saying “we are going to reject vibecoded PRs, unconditionally; so don’t bother submitting them.”

[-] ProdigalFrog@slrpnk.net 1 points 2 hours ago

The biggest contributor to the backlash of the proposed policy was the additional aspect explicitly not requiring AI used in a PR to be disclosed, regardless of its quality (and which is unrelated to the ability to quickly reject obvious slop PRs).

[-] nocteb@feddit.org 3 points 17 hours ago

You can be mad about that, but it has nothing to do with KDE.

[-] JustEnoughDucks@slrpnk.net 8 points 13 hours ago* (last edited 13 hours ago)

Except that the KDE contributors would be directly supporting it financially and giving it training data.

Also directly financially supporting technofascists and oligarchs.

Also directly financially supporting the destruction of the environment, stealing of water and electricity from the poor, bribary of politicians both local and international, and destruction of communities.

LLMs run by corporations are terrible and toxic, with very few exceptions. We also can't have a good faith argument and not acknowledge that the overwhelming majority of devs use those corporate datacenter models and not locally run models powered by home/company solar panels.

[-] naught101@lemmy.world 6 points 13 hours ago

Sure, it's an everywhere problem. But it would be nice to see more projects having strong preventative policies.

[-] nocteb@feddit.org -2 points 12 hours ago

I think it is more important to leave people the freedom to decide for themselves. It's not an opensource project's place to tell its contributers how to work as long as the contribution fits their requirements. No one's opinion is worth more than the other one's.

[-] PokerChips@programming.dev 6 points 19 hours ago

Sounds like a PR nightmare of AI tech debt to me. You're participating in the Shareen effect of the AI slop world.

[-] CameronDev@programming.dev 6 points 19 hours ago

Feel free to explain how "no change in acceptable quality" generates tech debt.

[-] sem@piefed.blahaj.zone 3 points 19 hours ago

Wtf is a shareen effect?

The top result is some missionary story https://www.mnnonline.org/news/shareens-story-a-divine-domino-effect/

this post was submitted on 24 Sep 2026
39 points (82.0% liked)

Linux

15040 readers
511 users here now

A community for everything relating to the GNU/Linux operating system (except the memes!)

Also, check out:

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

founded 3 years ago
MODERATORS