The article addresses that pretty directly:

> 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.

You can use zig just fine these days Ghostty, Tigerbeetle and bun before rust rewrite proved it. So i could care less if 1.0 lands next year or in 2033.

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.

There is likely some project out there that successfully used Brainfuck.

Doesn't mean much.

It's been in development since February 2016 and currently sits at version 0.17…

Would version 0.985117 be better?

You may have a point if zig have the budget of big cooptations or sponsors. It wasn't even full time until 2018 and went through COVID + other things.