A longtime Rust open-source developer spent time reimplementing their existing Rust JSONPath project, jsonpath-rust, as a new Zig library called zig-jsonpath, in order to directly compare the two languages. Coming from years of RustRover and JetBrains tooling, they found Zig's IDE support strikingly minimal, offering little more than syntax highlighting and basic autocomplete, which forced a return to more manual, low-level development habits.
besok.github.io
· 2026-09-19
Antfly, a startup building a document, full-text, vector and graph indexing database, has released version 0.2 of its engine rewritten entirely in Zig with no external dependencies controlling core logic. The original v0.1 engine was built in Go, chosen for its concurrency support and mature Raft implementation, but the team decided to rewrite the system early rather than iterate on it.
antfly.io
· 2026-09-15
A developer created an open-source tracing tool called buildprof that visualizes where time goes during software compilation on Linux, mapping every process and subprocess onto a single timeline. The project was sparked by a claim from Bun architect Jarred Sumner that Bun's new Rust build compiled over 5 times faster on Linux than its previous Zig build, a result the developer found suspicious given that the two builds used different link-time optimization settings—Full LTO for Zig versus ThinLTO for Rust.
lalitm.com
· 2026-09-12
A programmer describes using an AI system called Fable to convert a 65,000-line-of-code Go project into Rust, spending roughly $400 in the process. The approach relied on representing the codebase as data structures like graphs, state machines and constraints, then operating on those representations rather than translating code line by line, contrasting with a more mechanical file-by-file porting method used in an earlier Bun-to-Rust rewrite.
iurii.net
· 2026-09-01
Zig's main branch now supports pointer stability locks for std.ArrayList, a memory-safety mechanism previously introduced for Hash Map containers in 2024. Developers can call lockPointers() when holding pointers or slices into an ArrayList, then unlockPointers() once those references are no longer needed, preventing use-after-free bugs caused by reallocation. The feature originated from a pull request opened by contributor Leo Emar-Kar in 2025 and was documented by Robbie Lyman.
ziglang.org
· 2026-08-30
GoKawiil