Originally posted by @strycore in #6506: There are massive issues with AI tech, but those are caused by our current capitalist culture, not the tools themselves. In many ways, it couldn't have been...
It’s paraphrasing, but that’s pretty much what he said:
Quite honestly, if that’s the level of bugs we’re dealing with due to our use of AI tools, that’s a pretty good deal. I’ve seen much worse, so much worse in code that we actually shipped in releases. And no AI was used to create those critical bugs.
In what way is what I said false? His statement describes the bugs as a “pretty good deal” because he’s seen “so much worse” in his code without the inclusion of AI. Therefore, he’s cool with AI generated bugs because his code is already full of bugs.
Do you think he’s not cool with AI generated bugs in Lutris? Do you think the code isn’t full of bugs? Do you think the reason he’s cool with AI generated bugs isn’t because his code is already full of bugs?
It certainly seems like all of those elements are in what he said. He knows that the AI is introducing bugs (I pointed out two bugs that it introduced in that thread), and he’s fine with it (he said it’s a pretty good deal), because the code base was already buggy before (he’s seen so much worse in code he’s shipped in the project).
He kept challenging everyone in that thread to find below average code pushed recently. I took him up on it, and looked through his last four commits (all attributed to Claude) and found two bugs. He is totally fine with that. If it were me, I would really rethink using a tool that introduces bugs in half of its commits.
Considering how often and how heated the topic comes up in lemmy (even though the actual discussion takes place at GitHub) this is some sort of bullying.
Instead of simply parting ways some are harassing the developers of a free software in order to gain exactly nothing.
I’m involved in that discussion because I like Lutris and don’t want the project to suffer because of the use of AI tools. The developer challenged people in that discussion (myself included) to find low quality code that had been pushed recently from the AI. I did. Two of his last four commits introduced bugs.
You ain’t a dev or a maintainer oof the project, so keep the discussion civil. Also stop trying to rally people for your “cause”. At this point, you are just bluntly trying to make someone miserable.
I have no intention of making him miserable. I don’t think he’s a bad person, unlike some other people in that discussion. In my opinion, he was uninformed about the dangers of AI generated code. He was also uninformed about the quality of AI generated code, thinking that it wasn’t introducing bugs. Now he’s informed, but he is still going to use the AI. I’m hoping that’s just because he’s being stubborn. But, that’s something that people should know, so they can choose whether or not to continue using Lutris.
I was and still am a fan of Lutris, but I have switched to Bottles. Bottles is still missing some features that Lutris has, but I just can’t trust Lutris’ code and devs anymore. It makes me really sad, because the project itself is really cool.
I honestly, genuinely hope that he will see what a bad idea the AI code is before the project reaches an unmaintainable state.
These people are ridiculous. This is an open source side project, if people don’t want “ai slop” in their app, then maybe they should fork the project and maintain it themselves.
They can’t fork it now because the fact that the AI commits aren’t labeled as such means there’s no way to tell which need to be removed.
So… they can’t do that because they can’t tell the difference between the human code and the AI’s code? So that means that either A. The human code is also slop or B. The AI’s code is on par with the human’s code. This comment really proves that this aversion to AI is purely ideological.
But there was attribution, so you can easily check out commit before attribution was removed, use git blame on class attribution to see when it started, and fork before it.
They can. They just need to find the first instance of AI, branch from the commit before and start with that as a basis for master. Then push that branch to their own remote.
If someone cannot do that, they probably aren’t competent enough to maintain a project of this importance. They can then cherry pick commits that are good and merge those. Or request others recreate new PRS with them with correct attribution. It’s tedious, but easy.
Maintainership isn’t fun. The hardest problem is finding someone that cares enough to take it on. Many would give advice if someone was willing.
Sounds like Lutris dev was burnt out, so it would probably quickly replace it.
That’s not what he said.
https://www.merriam-webster.com/dictionary/libel
It’s paraphrasing, but that’s pretty much what he said:
Libel requires the statement to be false.
Holy shit you have AI derangement syndrome. If someone even mentions AI, then your instant reaction is to lie about it.
deleted by creator
Indeed. And your statement that you now describe as “paraphrasing” was false.
In what way is what I said false? His statement describes the bugs as a “pretty good deal” because he’s seen “so much worse” in his code without the inclusion of AI. Therefore, he’s cool with AI generated bugs because his code is already full of bugs.
It is false because it is not what he said, and does not have the same meaning as what he said.
Moreover, your misrepresentation is damaging to the developer’s reputation, and misleading to everyone reading here. Please stop.
In what way is what I said false?
Do you think he’s not cool with AI generated bugs in Lutris? Do you think the code isn’t full of bugs? Do you think the reason he’s cool with AI generated bugs isn’t because his code is already full of bugs?
It certainly seems like all of those elements are in what he said. He knows that the AI is introducing bugs (I pointed out two bugs that it introduced in that thread), and he’s fine with it (he said it’s a pretty good deal), because the code base was already buggy before (he’s seen so much worse in code he’s shipped in the project).
He kept challenging everyone in that thread to find below average code pushed recently. I took him up on it, and looked through his last four commits (all attributed to Claude) and found two bugs. He is totally fine with that. If it were me, I would really rethink using a tool that introduces bugs in half of its commits.
people are asking how exactly it is not/does not have the same meaning as what he said
Considering how often and how heated the topic comes up in lemmy (even though the actual discussion takes place at GitHub) this is some sort of bullying.
Instead of simply parting ways some are harassing the developers of a free software in order to gain exactly nothing.
I’m involved in that discussion because I like Lutris and don’t want the project to suffer because of the use of AI tools. The developer challenged people in that discussion (myself included) to find low quality code that had been pushed recently from the AI. I did. Two of his last four commits introduced bugs.
I know that you are involved.
You ain’t a dev or a maintainer oof the project, so keep the discussion civil. Also stop trying to rally people for your “cause”. At this point, you are just bluntly trying to make someone miserable.
There is nothing to gain for you.
I have no intention of making him miserable. I don’t think he’s a bad person, unlike some other people in that discussion. In my opinion, he was uninformed about the dangers of AI generated code. He was also uninformed about the quality of AI generated code, thinking that it wasn’t introducing bugs. Now he’s informed, but he is still going to use the AI. I’m hoping that’s just because he’s being stubborn. But, that’s something that people should know, so they can choose whether or not to continue using Lutris.
I was and still am a fan of Lutris, but I have switched to Bottles. Bottles is still missing some features that Lutris has, but I just can’t trust Lutris’ code and devs anymore. It makes me really sad, because the project itself is really cool.
I honestly, genuinely hope that he will see what a bad idea the AI code is before the project reaches an unmaintainable state.
These people are ridiculous. This is an open source side project, if people don’t want “ai slop” in their app, then maybe they should fork the project and maintain it themselves.
They can’t fork it now because the fact that the AI commits aren’t labeled as such means there’s no way to tell which need to be removed.
So… they can’t do that because they can’t tell the difference between the human code and the AI’s code? So that means that either A. The human code is also slop or B. The AI’s code is on par with the human’s code. This comment really proves that this aversion to AI is purely ideological.
Being able to see a difference in code quality is one thing; being able to prove who wrote the code for purposes like license compliance is another.
Based on the thread I originally linked, and the dev’s response, I think the answer is A.
But there was attribution, so you can easily check out commit before attribution was removed, use git blame on class attribution to see when it started, and fork before it.
What I’m saying is it’s probably not worth forking Lutris because it’s bad code. It would be better to just switch to a better alternative.
Like?
Heroic doesn’t work in all cases. I have to have both installed to use my library.
I’ve had many issues with other software and ended up having to use Lutris.
Lutris may have bad code, but functionally mature is generally what succeeds. Sexy code that doesn’t work exists on a handful of computers only.
Heroic + Bottles seems to cover everything I need, so I don’t need Lutris. I’m sorry if those don’t cover all of your needs.
They can. They just need to find the first instance of AI, branch from the commit before and start with that as a basis for master. Then push that branch to their own remote.
If someone cannot do that, they probably aren’t competent enough to maintain a project of this importance. They can then cherry pick commits that are good and merge those. Or request others recreate new PRS with them with correct attribution. It’s tedious, but easy.
Maintainership isn’t fun. The hardest problem is finding someone that cares enough to take it on. Many would give advice if someone was willing.
Sounds like Lutris dev was burnt out, so it would probably quickly replace it.