Every large company I've worked at has had many, many internal services using all sorts of different languages/frameworks.
Every large company I've worked at has had many, many internal services using all sorts of different languages/frameworks.
However people with less experience often assume those big companies have strategic directions for tech stacks, and that one teaming using something must be really important and implies bigger usage. I might even have assumed the same when being fresh out of university.
Therefore any news about "X is using Rust" seem to get a lot of traction.
Corollary is that the greater the fraction of reports of Rust usage that we see are about somebody in a big company, the lower the actual usage is.
Similarly, the greater the fraction of articles about Rust usage that carry on about how great it is, vs articles complaining about it, the less actual usage there is. Engineers are always limited by our tools, and we deeply resent those limitations. People complain a great deal about C++; the more useful it has turned out to be, the more complaints they have about it, and they are generally not shy about telling you them.
This makes more sense for tech companies. I work mostly for large banks and there definitely is less experimentation but there still is more experimentation than one would think (I have couple large Clojure projects very close in my org).
If the organization did not believe in potential of value from these ventures there would just be a small limited amount of languages to choose from because it is more economical when you consider support system. This is starkly visible in banks where there is huge need for development support system but no belief in value from ventures into obscure languages. The end result being that everything is written in Java and maybe couple other JVM languages (just because it is easy when you are already invested in JVM).
if the team doesnt like rust, they probably wouldnt use it less they are forced.