3 ms·

> they want to be able to make breaking language changes That sounds like it's not ready for production to me.

• drdexebtjl 3mo ago
  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.
  • uaksom 3mo ago
    > 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-an-Interface 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
    • drdexebtjl 3mo ago
      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.
      • uaksom 3mo ago
        Changing core features every few months doesn't seem very consistent...