Oh, a day later, I realized that there have been some of these questions of yours answered, but previously: > I also didn't see information about trade-offs ex

Oh, a day later, I realized that there have been some of these questions of yours answered, but previously: > I also didn't see information about trade-offs experienced in the transition to Rust on these projects. Yeah, I mean that's just not the topic of this particular post. But they have talked about it. Specifically this, from 2023: https://opensource.googleblog.com/2023/06/rust-fact-vs-fiction-5-insights-from-googles-rust-journey-2022.html https://opensource.googleblog.com/2023/06/rust-fact-vs-ficti... > I'm under the impression that it can take many engineers multiple years to begin to feel productive in Rust, is there any measure of throughput (even qualitative) that could be compared before, during and after that period? That is something that people say, but Google found differently. As that post says, "more than 2/3 of respondents are confident in contributing to a Rust codebase within two months or less when learning Rust. Further, a third of respondents become as productive using Rust as other languages in two months or less." On this one: > Were the engineers able to move as quickly in this (presumably) new-to-them language? Regarding "presumably," 13% had Rust experience, but the rest did not. They say "a third of respondents become as productive using Rust as other languages in two months or less" and "we’ve seen no data to indicate that there is any productivity penalty for Rust relative to any other language these developers previously used at Google."