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...
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.
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.