Yeah, in terms of "who is using Rust the most" inside of literal FAANG, least to most: * Netflix isn't using it at all, as far as I know * Google is using it

Yeah, in terms of "who is using Rust the most" inside of literal FAANG, least to most: * Netflix isn't using it at all, as far as I know * Google is using it in Fuchsia and Android, but I'm not aware of many web service things. Fucsia does use async/await though. Not sure about Android as I haven't examined it closely. * Apple is using it as the backend of services, and on some storage team, though for the latter I haven't heard from it in a while. They're absolutely async/await users. * Facebook/Meta are using it in a number of ways, for services but also as well as like, the SCM, filesystem, and build system. The latter aren't web services but do use async/await. * Amazon is using it heavily inside of AWS. You don't get more "web services" than that. But also, I meant "FAANG" in a broader sense. Large, established tech companies. Cloudflare, Microsoft, stuff like that. If you check out who is sponsoring the Rust foundation (not that that means that this gets you more weight for new features, mind you) https://foundation.rust-lang.org/members/ https://foundation.rust-lang.org/members/ it's very much not dominated by crypto or web3. When I was on the Rust team, we didn't prioritize web3/crypto use cases, and I haven't seen any evidence of that changing. It's always been kinda awkward, frankly. After writing this comment, I also wonder if maybe that's also not some of the disconnect here: while async/await is critical for network services in Rust, it's also useful for other things too. So you have a larger coalition than you may think that's interested in directing the language in that way.