Comment on Debian decides not to decide on AI-generated contributions
ProdigalFrog@slrpnk.net 5 days ago
I’m surprised they’re not adamantly against it, since AI code so frequently spits out garbage code, yet Debian is known for its stability. How can they not see the conflict here, especially to their reputation?
Venator@lemmy.nz 4 days ago
It can be good at generating boilerplate code or copying an existing solution, so maybe it might be useful for less critical parts such as adding a GUI for some feature that was previously limited to the command line…
ProdigalFrog@slrpnk.net 3 days ago
Unless that AI is hosted locally and only trained on GPL code (AFAIK, no AI model like that exists), it’s both unethical to use, and potentially corrupting the code-base with proprietary code it copied from somewhere else.
If a developer uses an AI hosted in a datacenter, then every use of it encourages the waste of water and fossil fuels to run the datacenter, it encourages the more to built in vulnerable neighborhoods where they can’t do anything about the pollution they generate, and it enriches the pocketbooks of the techno-fascists that run those datacenters.
Venator@lemmy.nz 3 days ago
Depends, in a lot of cases it costs them more money to service the query than they charge 😅.
Although it’s all borrowed money so it doesn’t matter to them…
Still causing all that havoc on the environment and poisoning with potentially proprietary stolen code though…
They’re gonna be running those data centers regardless though, as most of the cpmpute time is spent on training new models…
ProdigalFrog@slrpnk.net 3 days ago
Right, and they tend to convince investors to give them more by the amount of users adopting and using the product, which they can then extrapolate out with wild projections to convince venture capital to give them even more investments.
If more people abandon it entirely, the less venture capital they may be able to entice into their trap.
Venator@lemmy.nz 3 days ago
The copyright concerns can be mitigated somewhat by prompting to follow existing patterns in the codebase(and double checking that it has done that when reviewing the generated code)