Earlier quoted context omitted.
> Why use someone's project when you can just have the robot write your own? I've been thinking about this a bunch recently, and I've realized that the thing I value most in software now isn't robust tests or thorough documentation - an LLM can spit those out in a few minutes. It's usage. I want to use software which other people have used before me. I want them to have encountered the bugs and sharp edges and sanded…
> an LLM can spit those out in a few minutes. It may be able to spit out text that purports to be that, in a few minutes. But for most software, an LLM will not be able to spit out robust tests - let alone useful documentation. (And documentation which just replicates the parameter names and types is thorough...ly useless.)
The Zig project's rationale for their anti-AI contribution policy
241–250 of 496 posts
Re: The Zig project's rationale for their anti-AI contribution policy
#242I'm not sure how you could really take a stance on this. If someone used the tool to expedite work its unlikely you'd ever know it. If you use the tool to yeah, go one shot a ton of garbage then it will in fact be garbage.
It requires the people contributing the work to have the integrity to actually follow the project’s rules. It’s not OK to violate the project’s rules just because you don’t think you’ll be found out as a filthy fucking liar.
Re: The Zig project's rationale for their anti-AI contribution policy
#243Re: The Zig project's rationale for their anti-AI contribution policy
#244It seems like this policy will help them win at contributor poker in the short term, but lose in the end. The next generation of developers will, for better or worse, grow up using AI assistance to write their code, but none of them will ever become a Zig contributor.
Re: The Zig project's rationale for their anti-AI contribution policy
#245My issue with AI-generated OSS contributions is: If an AI improves developer productivity so much, why would maintainers of an OSS project want unknown contributors to sit in between the maintainer and the LLM? They'd be typing these queries into Claude Code themselves. To quote my colleague: > We do not need a middleman to talk to AI models. We are not bottlenecked by coding.
I suspect the people who claim that AI works by only giving it high-level instructions are mostly working on "mindless" projects where a developer in the weeds wouldn't need to think very much.
Re: The Zig project's rationale for their anti-AI contribution policy
#246My fraternity's national organization refused to take photos over email for the newsletter because they got a virus.
It's a short-sighted policy that's akin to "throwing the baby out with the bathwater."
Re: The Zig project's rationale for their anti-AI contribution policy
#247Earlier quoted context omitted.
Yep. I realised the same. No one reads docs, or goes through tests. Either ways it's easy to write useless tests. And easy to write useless docs. Idt most even read the code. Now the difference is that it has become possible to write useless code. So it's just the fact that others have already gone through the motions before I did. That's it really. I suppose in commercial settings, this is even more true and perhaps…
> No one reads docs, or goes through tests. I regularly do both when trying to use library, especially unfamiliar to me.
Re: The Zig project's rationale for their anti-AI contribution policy
#248Earlier quoted context omitted.
Do you think they skipped the main zig test suite or something? Only tested bun compilation? That seems unlikely to me
They didn't take into account the long-run impacts of the changes on future development, etc. I recommend reading the explanation given by one of the Zig devs, as it's a very clear and solid one.
Re: The Zig project's rationale for their anti-AI contribution policy
#249Earlier quoted context omitted.
Because you are at the whims of the bot they are at least partially dependent on.
You could extend that argument to any tool used by the developer, like a linter, sanitizer, the IDE itself, or even auto-completion. Why target LLMs specifically? The more I think about it, the more nonsensical it is. - What if I do everything by hand, but have an LLM review my work at the very end? - What if I have an LLM guide me through the codebase just by specifying the files I should read and in what order, but…
edit: Can't reply because I've posted a whole 4 times.
I believe we have different world views which is hardly a disagreement. Answering my question could pretty well highlight our difference of opinion.
Re: The Zig project's rationale for their anti-AI contribution policy
#250Earlier quoted context omitted.
An LLM most definitely cannot spit out robust tests or thorough documentation. It can spit out some tests or some documentation, but they will not cover the user perspective or edge cases unless those are already documented somewhere. That's verified by both experience and just thinking about it for two seconds. The sanding down you refer to is what generates those tests and documentation.
> but they will not cover the user perspective or edge cases unless those are already documented somewhere Are you suggesting that LLM's can't test for people who use screen readers? Keyboard only users? Slow network requests? You're acting like the issues an app faces are so bespoke to the actual app itself (and have absolutely no relation to existing problems in this space) that an LLM couldn't possibly cover it. A…
If you disagree with that, I think the onus is on you to show me that an LLM could simulate the full context in which a user interfaces with software. That's a ridiculous claim.
Feel free to show literally any evidence for this claim.