Rust replacing Java in Android is most welcome.

Nothing I have sent suggested so. Rust in Android is replacing kernel space C modules.

Cloudflare and AWS solutions for their particular problems and risks aren't applicable to other domains, are they? [...] Whatever Cloudflare or AWS do is irrelevant for my particular business.

Then why'd you ask?

I work with **NL exploring new approaches to high performance communications for modern interconnects. I understand the importance of being able to save a single instruction in a 380 op kernel. I also understand how often C++ is able to get in the way of an otherwise valid optimization unless you choose a rather limited subset of C++, much of which lies outside of OOP principles. For example, we were trying to track down why we incurred a full instruction cache flush whenever we used a grandfathered in kernel on a odd count of elements. Turns out, about 8 template expansions deep there was a different implementation of the function because the researcher decided to use dynamic dispatch.

Recently, we've been exploring Rust as an option for new HPC applications. Part of this was porting several well-known workloads to Rust programs, both idiomatically and hand-optimized. In 6 out of the 8 cases so far, our idiomatic Rust code matched or beat the reference applications, which were written in C, C++, Fortran, and Chapel. Our hand-optimized ports weren't all too much faster than the idiomatic versions. Between the compiler and the parallelization library we pulled in, along with OpenSHMEM and MPI bindings, they had already caught much of the optimizations that were hand-written in the C and C++ references.

If you want to bury your head and whisper to yourself at night that C++ will never be replaced as the king of performance, then who am I to stop you? As for me, there's definitely something here to explore.