[James_K]

Zig really annoys me. On the one hand, it seems like a very good language that I would find highly useful. But on the other, everywhere you look they remind out "it's not 1.0 yet" so anything you write might just stop working. I can't see how this is anything short of saying "don't use the language because we don't guarantee that anything you write will compile in future".

[kristoff_it]

Well it means that you can use the language if you are willing to rewrite some of your code from time to time because we don't guarantee backwards compatibility between updates. That's the nature of a work in progress project.

If you want to help us get faster to v1.0 consider donating :^)

[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 :^)