I have used the new template below to show how it looks. We can add more details to the linked CONTRIBUTING.md in the pop repo.
I have not included any LLM (also known as AI) generated content in...
Honestly, there are a few thoughts about this (and yes, some will be unpopular what I say).
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
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.
Also, good for security testing too.
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.
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.
It can actually do everything you mention, and under a watchful eye, generate reasonable code to spec. If you give it the architecture and requirements, it will make it as you see fit and generally faster than a skilled human.
But even beyond the theft, the resources required to do this are insane. The power and hardware needs are off the chart, and we’re still paying for all this with Monopoly venture bucks.
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.
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
As a retired senior programmer, I would have loved to use LLMs in the past for very specific things. I wouldn’t use it every day, but like every couple of months I had to do a massive refactor that took weeks to complete. I usually ended up writing codemod and just painfully changing tens of thousands of lines of code. Would be cool to just say “hey LLM, see how I did this one? Do the same thing everywhere else you find it. If you encounter anything that’s too different from my template just leave it for me to review”
Yeah, and that’s the stuff people don’t talk about
I have used it to do a lot of refactoring too. Vs code has been able to do basic refactoring for a while, but, it is also good for splitting up code into different files as an example (as long as you use a plan, it works well)
But, that’s because it’s also been trained how to do these tasks. And it isn’t really doing much with the code for them
For me it’s the exact extreme opposite than your first point: The LLMs as death of copyright could be an actual food thing.
The issue im struggling with is the ecological and economic harm. It feels a bit as if the steam machine would’ve been invented but you’d throw in babies in addition to coal.
For the plus sides you’re right (as in: I agree so it must be ;) )b- with one minor exception: the vibe coding part is not bad in itself. I actually used vibe coding as a very hard exercise: develop something and find ways to estimate its quality and performance but you are not allowed to look into the code! It’s a fun brain teaser because it forces a pure outcome-perspective. The code itself is irrelevant for this, it’s the mental training that’s really interesting.
Oh except people who publish vibe coded stuff as a cool new project without disclaimer. Or as PRs. Or as … Well anything where do see itself is actually important.
death of copyright could be an actual [g]ood thing
It could. It would assuredly be a boon to the development of de-build chains: decompilers and the like.
But, as long as Disney and Amazon get protections, I’m going to advocate for the protection of works by independent artists and coders, particularly CC-SA, GPL, or AGPL licensed works. This does mean resisting LLMs (and other generative AI) on copyright grounds. (Even if on the other hand I might advocate for the undoing of copyrights generally.)
And, even if that class of issue were settled, I also agree the current state of generative AI is a travesty to be resisted on ecological and labor terms. As just one example of ecological harm, MS undid years of sustainability work in service to Copilot. As one example of harming Workers, Amnesty International has identified human rights abuses in the training of several model brands.
The vibe coding thing IS bad though… The code being stolen isn’t the code generally written by big companies (because that’s in private repos)… It’s also stealing GPL / MIT code too, and not crediting it. And then the vibe coding bros take it, boast they made it, don’t give credit, don’t use it to improve AI, and they sell that code
I’d have no issue if it credited the original projects, but it doesn’t… And thats why nobody can hold them responsible.
The ecological harm is a fair point though. They’re setting up gas plants to run these things, instead of forcing renewables.
Oh the corporate bullshit I’m with you - but I’m opposed to copyright as a mechanism, that’s why I focused on it. Code can’t be “stolen” the same way a movie can’t be stolen in my book. That said:
With the crediting you’re absolutely right, I had not even thought about it and that’s not what I intended to imply. Thank you!
Although I lack the fantasy how this could look like. I’d be very happy if LLMs would be waived the “by” aspect as it’s in possible to link a generation to a dataset - but the training data has to be publicly available under the most generous licence consumed.
Honestly, there are a few thoughts about this (and yes, some will be unpopular what I say).
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.
It can actually do everything you mention, and under a watchful eye, generate reasonable code to spec. If you give it the architecture and requirements, it will make it as you see fit and generally faster than a skilled human.
But even beyond the theft, the resources required to do this are insane. The power and hardware needs are off the chart, and we’re still paying for all this with Monopoly venture bucks.
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.
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
As a retired senior programmer, I would have loved to use LLMs in the past for very specific things. I wouldn’t use it every day, but like every couple of months I had to do a massive refactor that took weeks to complete. I usually ended up writing codemod and just painfully changing tens of thousands of lines of code. Would be cool to just say “hey LLM, see how I did this one? Do the same thing everywhere else you find it. If you encounter anything that’s too different from my template just leave it for me to review”
Yeah, and that’s the stuff people don’t talk about
I have used it to do a lot of refactoring too. Vs code has been able to do basic refactoring for a while, but, it is also good for splitting up code into different files as an example (as long as you use a plan, it works well)
But, that’s because it’s also been trained how to do these tasks. And it isn’t really doing much with the code for them
For me it’s the exact extreme opposite than your first point: The LLMs as death of copyright could be an actual food thing.
The issue im struggling with is the ecological and economic harm. It feels a bit as if the steam machine would’ve been invented but you’d throw in babies in addition to coal.
For the plus sides you’re right (as in: I agree so it must be ;) )b- with one minor exception: the vibe coding part is not bad in itself. I actually used vibe coding as a very hard exercise: develop something and find ways to estimate its quality and performance but you are not allowed to look into the code! It’s a fun brain teaser because it forces a pure outcome-perspective. The code itself is irrelevant for this, it’s the mental training that’s really interesting.
Oh except people who publish vibe coded stuff as a cool new project without disclaimer. Or as PRs. Or as … Well anything where do see itself is actually important.
It could. It would assuredly be a boon to the development of de-build chains: decompilers and the like.
But, as long as Disney and Amazon get protections, I’m going to advocate for the protection of works by independent artists and coders, particularly CC-SA, GPL, or AGPL licensed works. This does mean resisting LLMs (and other generative AI) on copyright grounds. (Even if on the other hand I might advocate for the undoing of copyrights generally.)
And, even if that class of issue were settled, I also agree the current state of generative AI is a travesty to be resisted on ecological and labor terms. As just one example of ecological harm, MS undid years of sustainability work in service to Copilot. As one example of harming Workers, Amnesty International has identified human rights abuses in the training of several model brands.
The vibe coding thing IS bad though… The code being stolen isn’t the code generally written by big companies (because that’s in private repos)… It’s also stealing GPL / MIT code too, and not crediting it. And then the vibe coding bros take it, boast they made it, don’t give credit, don’t use it to improve AI, and they sell that code
I’d have no issue if it credited the original projects, but it doesn’t… And thats why nobody can hold them responsible.
The ecological harm is a fair point though. They’re setting up gas plants to run these things, instead of forcing renewables.
Oh the corporate bullshit I’m with you - but I’m opposed to copyright as a mechanism, that’s why I focused on it. Code can’t be “stolen” the same way a movie can’t be stolen in my book. That said:
With the crediting you’re absolutely right, I had not even thought about it and that’s not what I intended to imply. Thank you!
Although I lack the fantasy how this could look like. I’d be very happy if LLMs would be waived the “by” aspect as it’s in possible to link a generation to a dataset - but the training data has to be publicly available under the most generous licence consumed.
But that’s wishful thinking, I know.