[James_K]

Doing work on the Zig language would require writing more code than I would likely have to rewrite if I was to use it in the current state and fix the breaks. I want to use programming language without having to maintain it's compiler and without having the compiler devs periodically breaking my code. The fact that they haven't even outlined some subset of the language which is resistant to change basically means that all code written in it has maintenance requirements going forward. By contrast, I can write that same code in C and leave it for a while then have it all be fine when I come back.

[kristoff_it]

That's all fair, it just means that it's a bit too early for you to use Zig then.

The project can't come out already at v1 out of thin air, so it's a matter of being patient and waiting for the people working on it to make enough progress.

In the end it seems that all the writing around Zig has correctly communicated to you the state of things :^)