The Zig project's rationale for their anti-AI contribution policy
81–90 of 496 posts
Re: The Zig project's rationale for their anti-AI contribution policy
#82> why should a project maintainer spend time reviewing and discussing that PR as opposed to firing up their own LLM to solve the same problem? perhaps that's what the maintainers should be doing after all. it still takes time and tokens, though; neither is free. I'd personally rather have the maintainers spend the time writing as much docs and specs as possible so the future LLMs have strong guardrails. zig's policy…
Someone forking it and makeing it better with AI is a possibility. If that happens will know it was better for the project for the maintainers to just review the code. If that happens, they can probably become maintainers in the fork. Or maybe they don't like that work and could just go do something else
Re: The Zig project's rationale for their anti-AI contribution policy
#83Earlier quoted context omitted.
Depth of use over the lifetime of an app is a quality all its own that often not appreciated. A recurring pattern at $dayjob is that a new manager or director will join a business unit and declare an existing app as the worst terrible, no good, horrible app they've seen and they're going to fix that. A year and a half later the new app is finally delivered with 80% of the original functionality and a fresh set of bug…
Yes, see e.g. a quarter-century-old (!!) https://www.joelonsoftware.com/2000/04/06/things-you-should-...
Re: The Zig project's rationale for their anti-AI contribution policy
#84Earlier quoted context omitted.
How would you differentiate a 3000 line LLM commit made by the best models and good AI processes from a 3000 line commit made by the best human developer? edit Okay, I set the bar too high here with "best human developer" and vague "good AI processes". My bad. Yes, LLM is not quite there yet.
By using my brain.
Re: The Zig project's rationale for their anti-AI contribution policy
#85Re: The Zig project's rationale for their anti-AI contribution policy
#86Apparently, the noise around the AI policy came from Bun's developers saying that policy blocks upstreaming their performance PR. But the real reason seems to be that PR's code itself isn't in great shape, and introduces unhealthy complexity https://ziggit.dev/t/bun-s-zig-fork-got-4x-faster-compilatio... > Parallel semantic analysis has been an explicitly planned feature of the Zig compiler for a long time, and it ha…
Re: The Zig project's rationale for their anti-AI contribution policy
#87Earlier quoted context omitted.
How would you differentiate a 3000 line LLM commit made by the best models and good AI processes from a 3000 line commit made by the best human developer? edit Okay, I set the bar too high here with "best human developer" and vague "good AI processes". My bad. Yes, LLM is not quite there yet.
It's still fairly obvious just by skimming the code. The best AI models are still quite far from the best human developers in ability and especially in code quality.
We're already at the point talking about best vs. best.
Re: The Zig project's rationale for their anti-AI contribution policy
#88[flagged]
Re: The Zig project's rationale for their anti-AI contribution policy
#89Re: The Zig project's rationale for their anti-AI contribution policy
#90No human should trust any bullshit made by bullshit machine.