I looked around for work in Rust inside Google a year or so before I left and it was only some small parts of Fuchsia and not anything hiring at my site.
But I'm sure it's growing. But it won't be in the core Google3-on-Borg parts of Google, which are on the whole in either C++ or (increasingly) Go. Switching to a standardized garbage collected Google supported language makes sense in that domain. The "Carbon" stuff recently announced sounds interesting as well.
The long term looks good for Rust. But actual production code is still thin on the ground still everywhere.
(disclaimer: I work on Fuchsia, not speaking on behalf of my employer, feel free to clone the source repo and make your own analysis)
FWIW, to the best of my memory as of a year ago I counted ~1.1 MLoC of Rust code in our open source tree, with an additional ~1.3 MLoC in things we've vendored from crates.io.
There was a bit more C++ when I did the analysis, but it was the same order of magnitude.
Good to hear. A few years ago, there was a team advertising on grow/ for Fuchsia & Rust (for networking stuff I think), and they advertised in Waterloo but when I inquired, the posting went away and I was told they weren't actually hiring at my site. shrug Maybe it was my bad breath.
Other than that... Fuchsia was the thing that was rewriting all my work from scratch and killing everything I worked on (Chromecast on Home Hub, etc), so... :-)
But I'm sure it's growing. But it won't be in the core Google3-on-Borg parts of Google, which are on the whole in either C++ or (increasingly) Go. Switching to a standardized garbage collected Google supported language makes sense in that domain. The "Carbon" stuff recently announced sounds interesting as well.
The long term looks good for Rust. But actual production code is still thin on the ground still everywhere.