{"slug": "zig", "name": "Zig", "category": "other", "category_name": "Other software", "description": "", "recommenders": 6, "commenters": 10, "warners": 3, "score": 2.808, "rising": -1.96, "first": "2025-11-10", "latest": "2026-07-16", "why": "I personally think that Zig's combination of expressivity and simplicity, while still being low-level, is an unprecedented killer feature", "why_is_quote": true, "has_verdict": false, "sentiment": {"recommend": 6, "neutral": 1, "compare": 0, "warn": 3}, "spark": [2, 1, 0, 0, 0, 0, 1, 1, 1, 0, 0, 0], "listed": true, "loved": [], "caveat": "", "short_quote": "I personally think that Zig's combination of expressivity and simplicity, while still being low-level, is an unprecedented killer feature", "kind": "", "icon": true, "domain": "ziglang.org", "github_repo": null, "official_url": "https://ziglang.org", "pricing": "", "aliases": ["Zig"], "verdict": null, "praise": [{"label": "", "summary": "", "quotes": [{"id": 774922688, "item_id": 48432668, "url": "https://news.ycombinator.com/item?id=48432668", "by": "dnautics", "date": "2026-06-07", "stance": "recommend", "quote": "zig is reasonably established.  the llms write pretty good zig.", "excerpt": "> before Zig gets properly established. zig is reasonably established. the llms write pretty good zig. see project linked below which is almost entirely llm-written > And it is going to be very hard to justify choosing Zig for your sloppy-but-functional AI-written code why? because one project that was shipping fast made a dog's breakfast of it? > why open yourself up to memory unsafety on top of everything else? thi", "context": "", "use_case": "", "switched_from": "", "story": "My Software North Star"}, {"id": 770440673, "item_id": 48152542, "url": "https://news.ycombinator.com/item?id=48152542", "by": "Robdel12", "date": "2026-05-15", "stance": "recommend", "quote": "zig is upholding the quality and they hate it.", "excerpt": "https://ziggit.dev/t/bun-s-zig-fork-got-4x-faster-compilation-times/15183/19 > An example of this is the changes to type resolution which happened in the 0.16.0 release cycle\u2014these didn\u2019t affect users too much, but had big implications for the compiler implementation. Before those changes, the compiler\u2019s behavior was often highly dependent on the order in which types and declarations were semantically analyzed by the", "context": "", "use_case": "", "switched_from": "", "story": "Bun Rust rewrite: \"codebase fails basic miri checks, allows for UB in safe rust\""}, {"id": 742104688, "item_id": 46381543, "url": "https://news.ycombinator.com/item?id=46381543", "by": "smcnc", "date": "2025-12-24", "stance": "recommend", "quote": "I think Zig really shines here", "excerpt": "I think Zig really shines here: https://ziglang.org/documentation/master/#comptime", "context": "", "use_case": "", "switched_from": "", "story": "Comptime \u2013 C# meta-programming with compile-time code generation and evaluation"}, {"id": 737587808, "item_id": 46099238, "url": "https://news.ycombinator.com/item?id=46099238", "by": "lioeters", "date": "2025-11-30", "stance": "recommend", "quote": "it seems Zig's Wasm target does support SIMD", "excerpt": "I haven't dug deep but it seems Zig's Wasm target does support SIMD. > WebAssembly portable SIMD intrinsics https://codeberg.org/ziglang/zig/src/branch/master/lib/include/wasm_simd128.h", "context": "", "use_case": "Compiling to WebAssembly", "switched_from": "", "story": "Zigbook Is Plagiarizing the Zigtools Playground"}, {"id": 734067552, "item_id": 45879222, "url": "https://news.ycombinator.com/item?id=45879222", "by": "pron", "date": "2025-11-10", "stance": "recommend", "quote": "I personally think that Zig's combination of expressivity and simplicity, while still being low-level, is an unprecedented killer feature", "excerpt": "Turns out that \"killer features\" are frequently not killer enough. You mentioned Rust with its memory-safety killer-feature, and yet Rust is quite old now (about as old as Java was when JDK 6 came out or JS was when jQuery came out) and its adoption rate is low for such an old age. I have no idea if Zig will be successful or not, but even if you look just at memory safety, I think it does a better job at that than Ru", "context": "", "use_case": "low-level systems programming", "switched_from": "", "story": "Zig and the design choices within"}]}], "caveats": [{"label": "", "summary": "", "quotes": [{"id": 770250336, "item_id": 48140646, "url": "https://news.ycombinator.com/item?id=48140646", "by": "j-pb", "date": "2026-05-14", "stance": "warn", "quote": "https://github.com/ziglang/zig/issues?q=is%3Aissue%20label%3Amiscompilation", "excerpt": "Read through the stuff yourself if you don't believe me: https://github.com/ziglang/zig/issues?q=is%3Aissue%20label%3Amiscompilation", "context": "", "use_case": "", "switched_from": "", "story": "Remove .zig Files from Bun"}, {"id": 763058656, "item_id": 47691166, "url": "https://news.ycombinator.com/item?id=47691166", "by": "MarkSweep", "date": "2026-04-08", "stance": "warn", "quote": "All this to save a little memory CPU and memory usage? The juice does not seem worth the squeeze.", "excerpt": "I understand the stated reasons and disagree with their conclusions. It seems like a lot of extra work on the part of the Zig developers to have to reverse engineer undocumented interfaces. There is potentially extra work for the Windows developers if they want to change their private implementation details that Zig programs are now relying on. And in the case where the lower level APIs are missing features implement", "context": "", "use_case": "", "switched_from": "", "story": "Windows 95 defenses against installers that overwrite a file with an older one"}, {"id": 757668640, "item_id": 47354290, "url": "https://news.ycombinator.com/item?id=47354290", "by": "MintPaw", "date": "2026-03-12", "stance": "warn", "quote": "I just disagree that requiring constant maintenance is a good.", "excerpt": "I've never even heard of C3, I use C++ and Jai. I've never used Zig either, I just disagree that requiring constant maintenance is a good.", "context": "", "use_case": "", "switched_from": "", "story": "Zig \u2013 Type Resolution Redesign and Language Changes"}]}], "who": [], "tags": [], "use_cases": ["compiling to webassembly", "low-level systems programming"], "compared": [{"slug": "bun", "name": "Bun", "co": 2, "switched_from": 0, "switched_to": 0}], "makers": [], "threads": [{"url": "https://news.ycombinator.com/item?id=48933149", "title": "How Our Rust-to-Zig Rewrite Is Going", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=48389368", "title": "My Software North Star", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=48338673", "title": "Zig ELF Linker Improvements Devlog", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=48150900", "title": "Bun Rust rewrite: \"codebase fails basic miri checks, allows for UB in safe rust\"", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=48133323", "title": "Remove .zig Files from Bun", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=47565307", "title": "Windows 95 defenses against installers that overwrite a file with an older one", "mentions": 1}], "sentiment_by_month": {"2025-11": {"recommend": 2}, "2025-12": {"recommend": 1}, "2026-01": {}, "2026-02": {}, "2026-03": {"warn": 1}, "2026-04": {"warn": 1}, "2026-05": {"warn": 1, "recommend": 1, "neutral": 1}, "2026-06": {"recommend": 1}, "2026-07": {"recommend": 1}, "2026-08": {}, "2026-09": {}, "2026-10": {}}, "quotes": [{"id": 782982480, "item_id": 48936405, "url": "https://news.ycombinator.com/item?id=48936405", "by": "dabinat", "date": "2026-07-16", "stance": "recommend", "quote": "", "excerpt": "This is being worked on: https://rust-lang.github.io/rust-project-goals/2026/roadmap-fast-builds.html Most of the goals on this page are targeted for this year.", "context": "", "use_case": "", "switched_from": "", "story": "How Our Rust-to-Zig Rewrite Is Going"}, {"id": 774922688, "item_id": 48432668, "url": "https://news.ycombinator.com/item?id=48432668", "by": "dnautics", "date": "2026-06-07", "stance": "recommend", "quote": "zig is reasonably established.  the llms write pretty good zig.", "excerpt": "> before Zig gets properly established. zig is reasonably established. the llms write pretty good zig. see project linked below which is almost entirely llm-written > And it is going to be very hard to justify choosing Zig for your sloppy-but-functional AI-written code why? because one project that was shipping fast made a dog's breakfast of it? > why open yourself up to memory unsafety on top of everything else? thi", "context": "", "use_case": "", "switched_from": "", "story": "My Software North Star"}, {"id": 773456688, "item_id": 48341043, "url": "https://news.ycombinator.com/item?id=48341043", "by": "keithasaurus", "date": "2026-05-30", "stance": "neutral", "quote": "", "excerpt": "Working on something kinda similar. No GC, Python feel, managed memory, performance approaching C. It's here: https://blorp-lang.org if you want to compare approaches.", "context": "", "use_case": "", "switched_from": "", "story": "Zig ELF Linker Improvements Devlog"}, {"id": 770440673, "item_id": 48152542, "url": "https://news.ycombinator.com/item?id=48152542", "by": "Robdel12", "date": "2026-05-15", "stance": "recommend", "quote": "zig is upholding the quality and they hate it.", "excerpt": "https://ziggit.dev/t/bun-s-zig-fork-got-4x-faster-compilation-times/15183/19 > An example of this is the changes to type resolution which happened in the 0.16.0 release cycle\u2014these didn\u2019t affect users too much, but had big implications for the compiler implementation. Before those changes, the compiler\u2019s behavior was often highly dependent on the order in which types and declarations were semantically analyzed by the", "context": "", "use_case": "", "switched_from": "", "story": "Bun Rust rewrite: \"codebase fails basic miri checks, allows for UB in safe rust\""}, {"id": 770250336, "item_id": 48140646, "url": "https://news.ycombinator.com/item?id=48140646", "by": "j-pb", "date": "2026-05-14", "stance": "warn", "quote": "https://github.com/ziglang/zig/issues?q=is%3Aissue%20label%3Amiscompilation", "excerpt": "Read through the stuff yourself if you don't believe me: https://github.com/ziglang/zig/issues?q=is%3Aissue%20label%3Amiscompilation", "context": "", "use_case": "", "switched_from": "", "story": "Remove .zig Files from Bun"}, {"id": 763058656, "item_id": 47691166, "url": "https://news.ycombinator.com/item?id=47691166", "by": "MarkSweep", "date": "2026-04-08", "stance": "warn", "quote": "All this to save a little memory CPU and memory usage? The juice does not seem worth the squeeze.", "excerpt": "I understand the stated reasons and disagree with their conclusions. It seems like a lot of extra work on the part of the Zig developers to have to reverse engineer undocumented interfaces. There is potentially extra work for the Windows developers if they want to change their private implementation details that Zig programs are now relying on. And in the case where the lower level APIs are missing features implement", "context": "", "use_case": "", "switched_from": "", "story": "Windows 95 defenses against installers that overwrite a file with an older one"}, {"id": 757668640, "item_id": 47354290, "url": "https://news.ycombinator.com/item?id=47354290", "by": "MintPaw", "date": "2026-03-12", "stance": "warn", "quote": "I just disagree that requiring constant maintenance is a good.", "excerpt": "I've never even heard of C3, I use C++ and Jai. I've never used Zig either, I just disagree that requiring constant maintenance is a good.", "context": "", "use_case": "", "switched_from": "", "story": "Zig \u2013 Type Resolution Redesign and Language Changes"}, {"id": 742104688, "item_id": 46381543, "url": "https://news.ycombinator.com/item?id=46381543", "by": "smcnc", "date": "2025-12-24", "stance": "recommend", "quote": "I think Zig really shines here", "excerpt": "I think Zig really shines here: https://ziglang.org/documentation/master/#comptime", "context": "", "use_case": "", "switched_from": "", "story": "Comptime \u2013 C# meta-programming with compile-time code generation and evaluation"}, {"id": 737587808, "item_id": 46099238, "url": "https://news.ycombinator.com/item?id=46099238", "by": "lioeters", "date": "2025-11-30", "stance": "recommend", "quote": "it seems Zig's Wasm target does support SIMD", "excerpt": "I haven't dug deep but it seems Zig's Wasm target does support SIMD. > WebAssembly portable SIMD intrinsics https://codeberg.org/ziglang/zig/src/branch/master/lib/include/wasm_simd128.h", "context": "", "use_case": "Compiling to WebAssembly", "switched_from": "", "story": "Zigbook Is Plagiarizing the Zigtools Playground"}, {"id": 734067552, "item_id": 45879222, "url": "https://news.ycombinator.com/item?id=45879222", "by": "pron", "date": "2025-11-10", "stance": "recommend", "quote": "I personally think that Zig's combination of expressivity and simplicity, while still being low-level, is an unprecedented killer feature", "excerpt": "Turns out that \"killer features\" are frequently not killer enough. You mentioned Rust with its memory-safety killer-feature, and yet Rust is quite old now (about as old as Java was when JDK 6 came out or JS was when jQuery came out) and its adoption rate is low for such an old age. I have no idea if Zig will be successful or not, but even if you look just at memory safety, I think it does a better job at that than Ru", "context": "", "use_case": "low-level systems programming", "switched_from": "", "story": "Zig and the design choices within"}]}