

…elaborate? Anything that’s actually reliable?


…elaborate? Anything that’s actually reliable?


There’s a difference between “not being able to catch everyone” and having effectively no way to catch anyone.
And yes, unfortunately there are plenty of laws with the same issue (especially here and in the past decade or two) and it sucks - it only teaches people to ignore rules and a lot of them make you a criminal for no reason.


I disagree. For one, it’s unenforceable, just like outright banning it.
But AI assistance can also mean a lot of different things, from outright vibecoding through autocomplete up to only asking it to so review. It diminishes the human work in the eyes of other people, because a simple disclaimer doesn’t distinguish between the work done, and also encourages people to point out to AI as a scapegoat for their mistakes.
Good code always was and should always be one where a human is fully responsible for it; if you decide to vibecode and happens to end up with perfect code, good; if you write it fully yourself but it’s crap it doesn’t absolve you that you didn’t use AI…
It’s a tool, so use it responsibly like any other tool and stand behind your code no matter what tools you used.


Your previous post heavily implied that you preordered and are defending that despite your views.
By all means if you wait for the reception, some actual gameplay footage or reviews and like it, then by all means buy it.
The original commenter seemed to mostly complain about people preordering it blindly…
That can quickly get complicated, and more importantly noone does that.
People who want to do it generally. Just call for a “metadata tag” in the commit.
The thing is, what are you actually trying to achieve with this disclosure? How does it help you?
If you’re going to treat AI assisted code the same way you treat human code (with a ton of scrutiny - which you absolutely should), then what is the point?
Do you also want to know what IDE was used, which autocomplete engine, or what OS?