A quick google for something like "Who uses the Rust Programming language" turns up many lists of companies using Rust. Including such notables as Microsoft, Amazon, Cloudflare, Mozilla (of course).
Rust is also making inroads on the biggest project in the world, the Linux kernel.
So the future for Rust looks good. Hope so, a couple of years ago we bet our little start up on it.
Anyway, I firmly believe learning Rust is worthwhile anyway. It shows the directions any languages. in the future, that set out to do what Rust does, will go.
I like to believe that the impact of the Rust programming language is global. American companies represent just a small impacting fraction of what Rust is intending to do: which is, to help create safer and more stable programming practices, for everybody. The change from writing unsafe code to writing safer code ... can't happen fast enough.
Construction worker in Southern California. Normal guy, checking in.
Software although it changes fast, also seams to take forever to change. C still works.
I think Rust will be going on for a very long time. There may be a "name change", as happens sometimes. Maybe the foundation or some key member do something. Or just a culture shift in general. Something may cause a major fork someday (ie : libreoffice) but it won't change things for most of us. Our code will work for decades I believe.
The "ecosystem" part. I think that will change more. I think something will cause the crates.io and github grip to break and the ecosystem will become distributed. Or I hope so.
I trust the Rust Foundation of course, I mean, they compile my code. They have access to my system, if they wanted to. I just don't like the concept of everyone on the planet by default "checking in" every time they compile.
I really hope not. What you call distributed, I call fragmented.
I do not like the prospect of tooling like cargo-add and friends not working properly anymore because of it. And if they were updated to allow for multiple registries, it would make their UX considerably worse: instead of just requiring the crate name (which is easy enough to remember) you'd suddenly also need the registry to pull it from. Yeah I don't want to go registry hunting for the crate I need with just the right dependency tree. It just instantly creates a new form of dependency hell based on that alone, without considering any other potential complications.
And in fact, since it's all FOSS anyway, there isn't even a reason to unless the Rust Foundation somehow makes it necessary, which I don't expect they will.
While I'm sympathetic to this issue, in reality users are not checking in - it's not their personal info that's being sent, it's likely just an IP address, which is a (semi-)public piece of information. If you disagree with that assessment, it might be better to never visit any server ever again, since that same IP address is used to contact the servers of any other site you visit