4 ms·
A language which is not 1.0, and has repeatedly changed its IO implementation in a non-backwards-compatible way is certainly a courageous choice for production
by lewdwig 9mo ago
A language which is not 1.0, and has repeatedly changed its IO implementation in a non-backwards-compatible way is certainly a courageous choice for production code.
- steeve 9mo agothe upside is absolutely worth it
- Philpax 9mo agoIt's certainly not a choice I would have made, but there's sufficient precedent for it now (TigerBeetle, Ghostty, etc) that I can understand it.
- hu3 9mo agoalso Bun
- blue_pants 9mo agoalso Roc
- Iridescent_ 9mo agoThis one is far from prod-ready however
- ivanjermakov 9mo agoIn my experience, migrating small-scale projects takes from minutes to single digit hours. Standard library is changing. The core language semantics - not so much. You can update from std.ArrayListUnmanaged to std.array_list.Aligned with to greps.
- bluecalm 9mo agoRight? People must really like the design choices in Zig to do that instead of choosing another language. It's very interesting just because of that.
- dnautics 9mo agoSo, I'm noodling around with writing a borrow checker for zig, and you don't get to appreciate this working with zig on a day to day level, but the internals of how the zig compiler works are AMAZING. Also, the io refactor will (I think) let me implement aliasing checking (alias xor mutable).