top | item 46587598

(no title)

lewdwig | 1 month 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.

discuss

order

dnautics|1 month ago

So, 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).

ivanjermakov|1 month ago

In 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|1 month ago

Right? 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.

Philpax|1 month ago

It'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|1 month ago

also Bun

steeve|1 month ago

the upside is absolutely worth it