Earlier quoted context omitted.
From a software design standpoint, it certainly takes some adjustment going from OOP to the compositional architecture and structural trait system used by Rust, but it's not that big a shift. The biggest downsides are the poor standard library that ships with Rust and the non prescriptive project structure which puts too much authority on the writer to figure out. The biggest wins are that runtime exceptions and conc…
We've seen several anecdotes where JIT languages (e.g. Java) outperform Rust in throughput and latency in long-running server programs.
It's the fact that runtime errors are essentially impossible, making writing, reviewing, testing code very easy.
It also means LLMs can spin it out with the compiler, and if it compiles, it probably works. You just need to organize the code.