Not true! It just means (realizing a) vision is more important to them than becoming popular. It's their choice to make.
It's also a choice many of us wish in hindsight our tool makers had made.
""" This is a site designed to serve as a center for information - and by "center," we mean center. ByteCode.News is a site fed from discord, slack, IRC, and here on the web, meaning to present a common information graph and a common set of services. """
From my quick skimming of the site it just looks like hundreds of AI articles. More than likely it's just an AI bot that generates articles after some threshold of engagement is reached on "discord, slack, IRC".
There are lots of Ads that are posted as if they are articles for example: https://bytecode.news/posts/2026/10/cheerpj-5-launches-java-...
The article itself is just an extremely odd hit piece against Zig, I'd even be guess this is a form of "rage/engagement bait".
The important question is when/whether it will hit 1.0 and what its commitment to stability looks like _afterwards_.
> Zig has been under development for more than a decade. It remains at version 0.x, without a firm date for a stable 1.0 release.
> A programming language is infrastructure. Developers write applications and libraries against its syntax, standard library, compiler, and build tooling, and those interfaces determine how much of the surrounding ecosystem remains usable from one release to the next. In Zig, they seem to be forever changing, with the authors nigh-obsessed about breakage.
> The maintainers have a roadmap to 1.0, but that gives developers no meaningful indication of when they can expect the interfaces they depend on to stop changing. It may well take another decade.
If your "inherently unstable phase" is going to last multiple decades, you're not in a phase at all. You're just unstable.
If LLM are as good as people say why care about unstable API the LLM can help rewrite and fix it withing like 60 min.
I'm on the record as not a fan of Zig's management or choices, but this is among the many statements I disagree with in this article. The Zig team is writing (among other things) a compiler. If you don't want to become a compiler engineer, the maintainers are perfectly within their rights to decline to review your code or work with you further.
It's the other side of this that I take issue with. There are plenty of people who do want to become compiler engineers who see LLMs as a way of accelerating understanding by way of having a very well-informed (if not sometimes incorrect) chatbot be able to answer your questions and indulge your curiosity. IMO, it's these people that are the most let down by Zig's LLM policy.
Even less so, in AI driven development age, that the Zig community is notoriously against.
Interesting language for the last century, between Modula-2, Object Pascal, C, C++ and co.
In 2026, less Interesting.
Maybe not unavoidable product, but zig has a vision, do not need to go different direction or make product immediately or die
Thankful for the Hashimoto support of both organizations' financial sources: Zig Software Foundation and Ghostty via Hack Club. Thus both projects have external accountability. Hopefully that can help long term viability issues and alleviate the projects' social and financial pressures, as well as guide the projects technological and management choices. If that scaffolding didn't exist, I might not have chosen the platform.
You are saying they Zig is uninteresting because they don't want to pander to the current fads?
Let them cook. Perhaps they want to work on the core language for now, and maybe in 2-3 years time they can focus on the framework.
Or maybe they don't care about being popular. A passion project that is being worked on for a small group's enjoyment can still be interesting.
The point about constant compatibility breakage is the only valid one, but users are naturally self-selecting on that. I knew what I was getting into when I chose Zig. The upside is that the language isn't getting saddled by poor early designs (the "Writergate" breakage was a huge design improvement, as is the new Io interface). Also, it goes without saying that LLMs have dramatically reduced the cost of dealing with breaking changes, and the core team isn't going to stop you from using it.
I do wish there was a little less drama involved with Zig. Seems to be the curse of programming languages.
I also wish this article had a more... human touch. Not because of the phrasing etc, it just repeats itself a lot and a quick steer for brevity would have gone a long way.
> Its contribution policy excludes otherwise legitimate engineering workflows. [...] The recurring theme is that Zig's maintainers appear more interested in enforcing their vision of how software should be developed than making Zig a practical tool for people who want to build software.
I think a reasonable read of Zig's comments on LLM contributions is the volume and quality of human contributions is sufficient to sustain the project, and trying to accept LLM contribution creates more work than solutions.
And the author conflates contribution policy with downstream use of AI. Users are free to adopt all the AI tools they want on a Zig codebase. It is not true that, for users, "certain tools which might make it easier are unacceptable".
I for one don't personally agree with a bunch of Zig's choices (not bets that I'm interested in), but think most or all are reasonable in the space of possible trade-offs.
It’s fine for them to just be.
(python 2 to python 3 migration would have been less of an issue now as well)
It's more a toy of a small community of like-minded developers than a product for general consumption.
When Bun switched and they responded as they did the project confirmed that they aren't interested in serving the open market for developers, they're only interested in building something for themselves. Which is fine so long as all you're producing is the compiler; because all users, even those in their in-group, are subject to the stability problems with the language.
> The post criticized Bun's engineering practices, management, development culture, and business decisions. It described the foundation as relieved that the relationship was over and treated Bun as a liability (a term the Zig project seems particularly fond of when justifying its caprices). And all this in response to a project that had spent years using Zig, publicly promoting it, contributing to its ecosystem, and donating substantial amounts of money to its development.
They may as well have made their repos private and put up a notice on their website stating that they aren't interested in having users, please kindly withhold further inquiries.
Fayten makes a good point here https://news.ycombinator.com/item?id=50452445 About this article is 100% clickbait and 0 substance
So the complaints are: 1) that a 0.x versioned language which itself says is unstable and will break things for the sake of future quality, is breaking stuff? Shocking. Unbelievable.
2) they moved to codeberg. I think it absolutely is fair to say a project is going nowhere because they went from one git forge to another. It's a big migration for end users after all, you have to set a new remote for your origin
3) they do not use github sponsor anymore. Wonder if this is because they moved to codeberg. Unsure.
4) they wish for contributors to be engaged with the project and to stick long term.
5) they make "sweeping statements" on the quality of AI. Nothing I say here will convince you of anything unless you already agree with me, so I will spare my time and just say that given the point of view here is that AI is actually better than what Zig contributors think it is, and Zig contributors target version bump documentation breaking changes for humans, wouldn't this also directly clash with your idea that breaking changes take up a substantial amount of work for users of Zig? It's one or the other
This goes alongside "the language doesn't own its users" - a claim so ridiculous, the authors themselves have said plenty of times that, for example, if you wish to use AI to develop zig, you can, just not in the compiler project. What have they done which would make you think anyone at ZSF wants control over what you do and how you do it?
Overall I feel like this is complaining for the sake of complaining. I am also willingly going to ignore the blatant AI writing style (I'm sure that's just the way OP writes though) and the site which I feel like I can confidently say with which model and what effort level it was generated.
Do better
That's why ISO is committee-based (democratic), despite the issues and slower speed, that process is better suited to
You can always make a fork of Zig called "Zack"....
Is it 1.0 yet?
The whole point of not being stable yet is so that you can try things out and see what actually makes sense before committing to it for all time.
(Counterpoint: C++, JavaScript xD)
I guess it has been like 10 years at this point though.
The way I read it, the post seems to argue they have enough users already to seriously consider cutting the first stable release.
Zig foundation is a non-profit with their mission being educating the "next generation of programmers". They decided against AI usage and I for one am grateful for a last corner on the internet that caters to the craft as opposed to literally every other community that has been reduced to discussing agent loops.
Again, ignoring the AI fingerprints of the article, all the criticism boils down to it being a project catering to different needs. You are free to fork it, name it Zag and run Claude on it to create the language of your dreams.
Master Foo, who gains more merit? He who writes ten thousand lines?
Or he who, recognizing the emptiness of the endeavour, writes zero?
personally, I'm more alarmed that they're dropping LLVM in favor of their own backend.
good luck, boys.
Long-term, we do want to compete with LLVM for optimized builds too, but there are no plans whatsoever to drop LLVM support.
Just because AI bros can't put "Zig compiler" contributor on their linkedin page or CV doesn't make it an shit language.
There should be no slop code, no slop words, NO WAY TO TELL.
I couldn't give less of a shit if you use AI if nobody in the world could possibly tell. But that's not what any of this is about.
> No LLMs for finding bugs.
Good luck with that in the era of LLM-discovered security vulnerabilities.