I am not a 10x systems programmer but I have used both for MCU projects.
An expert Rust programer probably wouldn't have the same friction points I experienced.
Two of the main advantages of the Rust borrow checker is preventing use after free and iterator invalidation.
Zig's deferred free helps with the first, and hardware FIFOS, doorbells etc often caused me to have a non significant amount of unsafe code.
For me, the array safety in Zig removes most of the C foot guns, and the Rust projects decision to error on the constrained side of the static analysis dichotomy was getting in the way.
It isn't even a case of one being 'better' for me, the tradeoffs just made Zig better for this use case for me.
Comments
I am not a 10x systems programmer but I have used both for MCU projects.
An expert Rust programer probably wouldn't have the same friction points I experienced.
Two of the main advantages of the Rust borrow checker is preventing use after free and iterator invalidation.
Zig's deferred free helps with the first, and hardware FIFOS, doorbells etc often caused me to have a non significant amount of unsafe code.
For me, the array safety in Zig removes most of the C foot guns, and the Rust projects decision to error on the constrained side of the static analysis dichotomy was getting in the way.
It isn't even a case of one being 'better' for me, the tradeoffs just made Zig better for this use case for me.