Zig 0.17.0 brings incremental compilation to x86_64-linux

Zig v0.17.0

Zig 0.17.0 lands after five months and 925 commits from 206 contributors, reworking the build system with a new Build Server Protocol and upgrading the ELF linker so incremental compilation is expected to work for everyone on x86_64-linux. The release also adds a formally specified and fuzzed grammar, moves C translation to an external package, and introduces SafeAllocator, while dropping several legacy syntax forms.

Originally predicted to be shorter, this release cycle ended up substantial, with the Build System reworked, including the introduction of the Build Server Protocol, and the ELF Linker enhanced to the point where we expect Incremental Compilation to work for everyone on x86_64-linux.
  1. audunw

    Would recommend checking out the Zig state of the (tagged) union as well.

    https://youtu.be/zwi5b5xSsKA?is=PTjJJjSnVMdRuZag

    It may surprise some people here to see that Andrew is warming up to using LLMs to discover bugs (inspired by results from SQLlite) and considers it a tool on the path to getting to bug free software.

  2. ubavic

    I’ve written software for a living in JS, C, Pascal, and Go, and I’ve tried many, many more languages. After working on a project in Zig for a year, I’m convinced that Zig is the best-designed language I’ve tried so far. Haskell comes close. At least, it’s the best-designed language for humans.

    It’s not for everyone yet. It’s still unstable, and its ecosystem is small. However, both are improving.

  3. vitaminCPP

    I'm always impressed by Zig's targets support. I'm starting to think that it might be the only language that competes with C on this regard.

    I'm looking forward to see what the new build integration can unlock on the tooling side.

    What I'm looking for the most for the next release(s):

    - New stackless coroutine IO implementation

    - First class fuzzer tooling

  4. vikrantrathore

    Congratulations to zig team. Good to know they are trying pragmatic approach to LLM now. I left the zig eco-system due to zig core members hostile behaviour toward humans not just LLM, so good to see the change they are becoming pragmatic. For me I am slowly porting the same work to odin language [1].

    Background is I created issue and one pull request to fix them in zig compiler version 0.16.1 issue numbers 36812, 36811 (you cannot access them as my account is banned can see my fork at [2]). Respecting the community’s no AI stand. For these specific issues I wrote the issue and code myself and not let AI write it. Spend a lot of time on it. Subsequently without any notice my account was banned because my projects on github using zig uses LLM. This was done without message or any information. My account was banned on zig repository.

    I can now understand the other side of coin how bun team might have been treated with disdain when they used LLM.

    I wrote an email and left the zig community, have many work in zig but slowly moving them to odin.

    I feel personal disdain should not be spilled on to people who are pragmatic on using LLM. I was a very big evangelist of zig for their no LLM stand and promoted them among my community, but with poor treatment by community I just left. You can still see projects I wrote in zig [3].

    I have worked with postgreql community since 1997 and python community since 1998. Never felt such hostile community. So all the best and I wish zig continue i […]

  5. jabedude

    How is Zig doing as a project? I remember they took a hard line against AI

  6. osigurdson

    Curious as to the state of evented IO / io_uring in this version.

  7. luiwammus

    Although I understand that upgrading LLVM version is a lot of work, it's a bit frustating that loop vectorization is still disabled.

  8. ErenayDev

    https://ziglang.org/news/0.17.0-released/

More from this day

2026-10-02