upvote
This might be true, but we can continue to try and require the communities we have been part of for years to act a certain way regarding disclosures.

If the community majority changes it mind then so be it. But the fight will continue for quite some time until that is decided.

reply
There never was a cohesive generic open source community. There are no meaningful group norms. This was and always will be a fiction.

I’m tempted to just start putting co-authored-by: Claude in every commit I make, even the ones that I write by hand, just to intentionally alienate people like you.

The best guardrails are linters, autoformatters, type checkers, static analyzers, fuzzers, pre-commit rules, unit tests and coverage requirements, microbenchmarks, etc. If you genuinely care about open source code quality, you should be investing in improving these tools and deploying them in the projects you rely on. If the LLMs are truly writing bad or broken code, it will show up here clearly.

But if you can’t rephrase your criticism of a patch in terms of things flagged by tools like those, and you’re not claiming there’s something architecturally wrong with the way it was designed, you don’t have a criticism at all. You’re just whining.

reply
> There never was a cohesive generic open source community. There are no meaningful group norms. This was and always will be a fiction.

It's always been a bit splintered, but it was generally composed of 95%+ of people that know how to program. That is no longer the case in any sense.

> I’m tempted to just start putting co-authored-by: Claude in every commit I make, even the ones that I write by hand, just to intentionally alienate people like you.

I mean it sounds like you are already using claude for everything so this is probably a bit of a noop lol.

> But if you can’t rephrase your criticism of a patch in terms of things flagged by tools like those, and you’re not claiming there’s something architecturally wrong with the way it was designed, you don’t have a criticism at all. You’re just whining.

No, because doing that requires MORE rigor and work than what an LLM driven project had put into it. That difference in effort/work is not tenable, its shallow work being shown, its shallow criticisms thrown at it.

All sense of depth and integrity is gone and killed.

reply
I tried to control LLM output quality by different means, including fuzzing. Had several cases when LLM "cheated" on that too. So, I have my own shades and grades of being sure the code is not BS.
reply
I see this as the same argument as saying GMO label not needed, no need to mention artificial flavours in food, etc.

I mean this in the nicest way possible: the world is just going to insist that AI generated output is marked clearly as AI produced output.

Not sure whether giving a LICENSE even makes sense.

reply