It’s sad to still see comments like this. You don’t necessarily pick Rust for the performance or the memory safety, or whatever rustaceans tout. I think this ar

It’s sad to still see comments like this. You don’t necessarily pick Rust for the performance or the memory safety, or whatever rustaceans tout. I think this article summarizes pretty well why I love building apps un Rust: the code you write is robust as hell. It builds? Virtually only logic errors are left (and a null or error test is not a logic error in my book). And have you ever built non-system things using Rust? Because I do write, among other things, gRPC services professionnaly, and let me tell you lifetime errors are virtually nowhere to be found. Why? The vast majority of apps are request-response things with owned data in, owned data out; no manual memory management either. And on the rare occasions the nitty-gritty parts of the language do surface, it is well worth it due to the peace of mind that the code is robust. Just pattern matching on errors is enough for me to write APIs in Rust and not Go. As an added bonus, we use the same language for our APIs, system agent, low-level network apps, eBPF probes, you name it. It makes work so much more fluid for the whole team. However I do agree on some parts, esp. the explicit yields, where Go and Zig nailed it. Async is currently somewhat of a pain in Rust, especially since it tends to infect pretty much anything. I don’t remember the last thing I wrote without tokio…