Zig breaking change – Initial Writergate

And this is exactly why you do not use shiny new languages for your projects. Hope tigerbeetle won't have too much trouble with this

This is exactly why we chose Zig.

Andrew’s design decisions in the language have always been impeccable. I’ve never seen him put a foot wrong and would have made the same change myself.

This is also not new to us, Andrew spoke about this at Systems Distributed ‘25.

Also, TigerBeetle has and owns its own IO stack in any event, and we’ve always been careful to use stable language features.

But regardless, it’s in our nature to “do the right thing”, even if that means a bit of change. We call this “Edge” and explicitly hire for people who have the same characteristic, the craftspeople who know how to spot great technical quality, regardless of how young (or old!) a project may be.

Finally, I’ve been in Zig since 2018. I wouldn’t exactly call it “shiny new”. Zig already has the highest quality toolchain and std lib of anything I would use.

Good to know, also thanks for the detailed reply! Glad you are fully aware of these nuances, but it also doesn't surprise me considering your amazing presentation of Tigerbeetle! Much success in the future.