Returning to Zig after losing trust in Rust's governance
jonathandeamer
21 points
13 comments
July 05, 2026
Related Discussions
Found 5 related stories in 802.3ms across 14,015 title embeddings via pgvector HNSW
- Returning to Zig birdculture · 15 pts · July 05, 2026 · 82% similar
- How Our Rust-to-Zig Rewrite Is Going jorangreef · 467 pts · July 16, 2026 · 66% similar
- Zig 2026: No-AI Policy, $670K Foundation, Left GitHub and Why Zig Isn't 1.0 [video] doppp · 33 pts · May 28, 2026 · 64% similar
- Zig: Build System Reworked tosh · 338 pts · May 30, 2026 · 60% similar
- Zig Zen Update tosh · 121 pts · June 06, 2026 · 58% similar
Discussion Highlights (6 comments)
znpy
> When the biggest companies in the world are each giving you hundreds of thousands of dollars per year, you probably don't want to upset them. Don’t forget that those money ultimately go to individuals, that often willingly sacrifice their opinions and positions for the fat paycheque.
sscaryterry
The author has a point. You STILL need a github account to publish to crates.io.
littlestymaar
TL;DR; the author feels betrayed because the Rust leadership didn't take a strong stance against LLMs like the Zig team did. IMHO LLMs are causing lots of issues in the software world, especially in the open source communities but I don't think Zig's blanket rejection of everything AI-related is a good thing.
Ygg2
> Meanwhile, Rust took its time. Yes, this is the difference between a BDFL. A single person can make a decision faster, than a group of people. And consensus often leaves most people a bit miffed. Again, the issue starts when the dictator grows mad and starts making decisions that make every contributor uncomfortable. > To my horror, many software projects were accepting LLM-generated code. I had thought LLMs were unpopular among developers. Why would a really stochastic auto-complete and analyzer be disliked by developers? LLMs are a useful tool, sometimes, but they aren't the <WE WILL REPLACE ALL WORKFORCE BY 2028> levels of hype that current frontier labs need to justify their costs. > But Memory Safety! I'd be genuinely flabbergasted if Zig ends up as safe as Rust without any overhead. So, no, adding Fil-C doesn't count. We have memory safety with overhead. We call it Java/C#/JavaScript/Go/<INSERT VM LANG HERE>.
atdt
The money contributed to the Rust Foundation by large corporate members supports initiatives[0] that benefit all users of Rust, and I am happy for it. The slow and deliberative approach the Foundation took to crafting the AI policy, and even the hedging language in the policy itself, are indicators of a healthy open organization. The author's scorn shows immaturity. [0]: https://rustfoundation.org/#initiatives
RustSupremacist
501(c)(3) organizations are non-profits that include charities, whereas 501(c)(6) organizations are non-profits with less strict requirements. Both are tax-exempt federally, but 501(c)(3) organizations have higher financial transparency requirements and higher restrictions on political activity (which qualifies donations to 501(c)s as tax-deductible). The Rust Foundation is a 501(c)(6) and not a 501(c)(3). The Rust Foundation would do better for the community if they were a 501(c)(3) and more transparent about finances. The Rust Foundation should change their governance structure to a 501(c)(3) instead of a 501(c)(6).