AlpineBSD

Discussion overview

The thread spent far more time on AlpineBSD’s AI policy than on the new BSD distribution itself. Its defining move is a hard ban on AI-generated contributions, extending to pinning core toolchain components at versions believed to predate LLM-written code, while still allowing AI to inspect code. Supporters see that as an unusually coherent attempt to preserve a codebase whose provenance can be trusted, rather than merely asking contributors to behave responsibly after the fact. They argue that a project is entitled to reject the AI development pipeline outright and build a community around that boundary.

Critics see the rule as symbolic purity with a punishing maintenance bill. Freezing GCC, binutils, and GDB could cut AlpineBSD off from upstream fixes and force a small project to own increasingly difficult forks; a ban also cannot establish that C code is safe, correct, or even genuinely AI-free. Several readers wanted the project to explain its threat model and practical goals instead of treating the rationale as self-evident. The exchange broadened into a view of free software splitting into anti-AI, reluctant-AI, and AI-forward camps, with some expecting healthier self-selection and others warning that AI adopters are ignoring licensing and provenance risks.

Points of disagreement

The core fight is whether a strict AI-free policy is principled supply-chain control or unproductive tribalism. Defenders say refusing generated code is the only credible route to a genuinely LLM-free project and a community that rejects a damaging development culture; critics say auditability and code quality matter more than authorship, while toolchain freezes make the policy operationally self-defeating.