this post was submitted on 01 Oct 2026
544 points (97.7% liked)

Linux

15106 readers
415 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
 

Fingers crossed Gnome follows suit! :)

you are viewing a single comment's thread
view the rest of the comments
[–] auzy1@lemmy.world 32 points 1 day ago* (last edited 1 day ago) (16 children)

Honestly, there are a few thoughts about this (and yes, some will be unpopular what I say).

  1. There is the ethics problem of how LLM is trained. It is a theft machine. Thats why companies love it, because they can steal work and profit
  2. However, people WRONGLY assume AI is exclusively for Vibe coding. When used by Senior/real developers, it is super useful for writing tests and code reviews. Some of the issues I've found in our old code from 10 years ago, were never reported (or, we had reports, but always assumed it was something else). There are tools for code review (and have been for a long time), but AI has stepped it up. In well designed / stricter languages, you can avoid a lot of errors that AI is good at detecting, but, it is still super valuable for this stuff.
  3. Also, good for security testing too.
  4. The biggest issue are untrained slop cryptobros, who throw money at it, and can't test (or understand) their code. Then it wastes other devs time reviewing it and identifying the 50 regressions it causes.
  5. We've had cases where I've had to argue with customers that Claude is telling them bullshit. From the support side, it has made things WORSE.

I'd argue it isn't actually a good thing necessarily to ban using it as a tool entirely from senior devs.

The biggest issue at the moment are arrogant junior cryptobros who are too lazy to learn to code, and just want to throw money at the issue. And that wastes everyone's time.

What we really need is a ethical AI model that only uses completely open code, pays people for their code (instead of just stealing it). and a way to ensure it is only used by developers who can use it properly. Ideally, only allow that code to be used for open source too

I actually wouldn't want to see Gnome/System76 completely ban it. What I would want to see is for it to be permitted for approved devs with VERY specific guidelines dictating how it can be used.

[–] HaraldvonBlauzahn@feddit.org 11 points 1 day ago* (last edited 1 day ago) (3 children)

The issue for now is LLM generation of code, not code auditing.

And no, I don't give a fuck whether some genius in theory could paint s new Mona Lisa with it. The issue us how it is used in practice, most of the time, today. At $WORK, I have a severely ai-pilled Senior Embedded Software Architect which hasnt managed in one and a half year to set up a working driver for a RS232-controlled stepper motor, from a port of previously working code. A thing that should take a week at most. I had to educate him that in C++ drivers, you need to use locks or mutexes to access variables that are concurrently changed and read from several threads. AI enables catastrophic levels of incompetence.

And FOSS projects need to protect themselves against that.

[–] auzy1@lemmy.world 7 points 1 day ago (1 children)

Yeah.. LLM Generation I agree is the biggest issue by far.

On the Kernel side, code review though apparently has been a big factor apparently, because people are testing kernel modules in seriously dumb tests that would never happen in practice, and then submitting some of the dumbest patches to protect against faults that won't happen in reality

[–] jj4211@lemmy.world 1 points 15 hours ago

Oh man, the insane defensive code that it wants to generate. Yes, a decent principle, but when the stack has checked the same thing like 4 times, it's a bit much.

load more comments (1 replies)
load more comments (13 replies)