1,488 karma · joined June 19, 2013
Not sure about Rust, but Zig seems to explicitly follow Cathedral-style development model.
String theory doesn't work this way, whatever was measured will be explained as an afterthought by free parameter tuning.
Rust approach to shared memory is in-place mutation guarded by locks. This approach is old and well-know, and has known problems: deadlocks, lock contention, etc. Rust specifically encourages coarse-granular locks by design, so lock contention problem is very pressing.
There are other approaches to shared memory, like ML-style mutable pointers to immutable data (perfected in Clojure) and actors. Rust has nothing to do with them, and as far as I understand the core choices made by the language make implementing them very problematic.
A CLI tool (which most POSIX tools are) would pick throughput over latency any time.