Why not go? Slower than rust. Type system is lacking.
Why not c? Not memory safe.
Why not c++? Also not memory safe.
Why not zig? Not memory safe.
Why rust? Fast, memory safe, type safe. Compiler pushes back on LLM hallucinations and errors.
Over time, security-critical and performance-critical projects will autonomously be rewritten in rust.
That’s not a bad thing though. It’s okay to aim for your thing and be good at just that. No need to try to please everyone.
On the other hand, I constantly have to jump through hoops in javascript. You literally cannot compare two objects for structural equality in JS without jumping through hoops. It’s unbelievable. Yet no one says javascript is not versatile enough to be used in high level contexts.
It is fair to say that the way Rust deals with closures requires too much hoop-jumping to make a truly ergonomic reach equivalent
As hobby projects go it’s “in production” with maybe 50 active users, so nothing crazy. Definitely less ambitious than a sqlite successor. But it’s not trivial. (The repo history is truncated to save money on github LFS storage.)