The Zig project is going nowhere

Zig is presented as a technically promising systems language whose project management is making it increasingly difficult to recommend. The central complaint is that Zig remains in perpetual pre-1.0 flux after more than a decade: releases such as 0.15, 0.16, and 0.17 repeatedly change language, standard-library, I/O, and build interfaces, forcing users to rewrite code, update dependencies, or freeze on old compilers. A roadmap offers no clear date for stability, leaving developers to absorb ongoing migration costs. The criticism extends to Zig’s contribution rules, which prohibit not only AI-generated submissions but also AI-assisted editing, research, and debugging. The argument is that maintainers judge contributors’ tools and commitment, not just whether their work is correct and useful, creating an exclusionary culture while users are already expected to keep relearning a changing language.

The departure of Bun, a prominent Zig-based JavaScript runtime, is offered as evidence of the practical consequences. Bun cited memory-safety problems involving Zig’s manual memory management and JavaScript’s garbage collector, and said Rust’s ownership model better suited its needs. Maintaining a customized Zig compiler and friction around upstream contributions also added costs. Rather than treating the move as feedback from a major user, Zig’s leadership publicly attacked Bun’s engineering, management, and culture, later revising its remarks. The critique argues that users owe a language no permanent loyalty and that maintainers should respond to criticism without personal hostility. Zig’s move from GitHub to a less established, unreliable hosting service is also cited as another decision that prioritizes maintainers’ preferences over users’ practical needs.