How Our Rust-to-Zig Rewrite Is Going

Re:How Our Rust-to-Zig Rewrite Is Going by rwz on Thursday July 16, 2026 @12:33PM (#48936768)

> they want to be able to make breaking language changes

That sounds like it's not ready for production to me.

[ Parent | on HN ]

Re:How Our Rust-to-Zig Rewrite Is Going by drdexebtjl on Thursday July 16, 2026 @12:59PM (#48937095)

I invite you to read the release notes and see for yourself the types of breaking changes we’re talking about.

To me it is not much different from Lua, which despite being on 5.x for decades, makes breaking changes on minor releases (because it predates SemVer).

I also don’t see it being much different from any other language or language runtime that has a major release every year.

It’s fine to update at your own pace.

[ Parent | on HN ]

Re:How Our Rust-to-Zig Rewrite Is Going by uaksom on Thursday July 16, 2026 @03:48PM (#48939374)

> I invite you to read the release notes and see for yourself the types of breaking changes we’re talking about.

I did, and I immediately found this in the latest release: https://ziglang.org/download/0.16.0/release-notes.html#IO-as...

That seems like it would require changing a lot of code. Calling it "production ready" is dishonest at best

[ Parent | on HN ]

Re:How Our Rust-to-Zig Rewrite Is Going by drdexebtjl on Thursday July 16, 2026 @06:00PM (#48940844)

Not really. It’s find and replace work.

If by production-ready you mean you can forever avoid changing code you wrote 8 months ago, sure, pick something else.

To me production-ready means it can be trusted to power production workloads, has all tooling I need, and has a consistent long-term vision. Zig ticks all the boxes.

[ Parent | on HN ]

Re:How Our Rust-to-Zig Rewrite Is Going by uaksom on Thursday July 16, 2026 @07:06PM (#48941465)

Changing core features every few months doesn't seem very consistent...

[ Parent | on HN ]