Really fine points. Rust definitely has more going for it than some of the earlier hype cycles. That being said, and speaking from my own experience with Rust,

Really fine points. Rust definitely has more going for it than some of the earlier hype cycles. That being said, and speaking from my own experience with Rust, there are some design choices that I suspect may pose a barrier for its widespread adoption. Rewriting small discrete components while maintaining C interop is a very fine use case for Rust - building and maintaining a large, complex, and stateful system wholly in Rust is quite another. I'd be very, very surprised if Microsoft switched en masse to Rust for their bare metal stack, at least with Rust in its current shape. Clojure is a great parallel to bring up here, and should serve as a cautionary tale for Rust: Java was unpopular, Clojure showed that a better way was possible - but was itself just a bit too alien and hard to work with for many Java devs - so the more-familiar Kotlin swept in and carried the day. I have a sneaking suspicion that this might happen again, with C/C++ in the role of Java, Rust in the role of Clojure, and _ in the role of Kotlin. I don't quite know what the _ will be yet, but I suspect it will be a lot more accommodating to grizzled C wizards than Rust is. (I'm keeping an eye on Zig.)