Rust developers at Google are twice as productive as C++ teams

Previous discussion: [0](56 points, 3 days ago, 32 comments)

[0]: https://news.ycombinator.com/item?id=39851872

There is a large difference in churning out code for a new project compared to trying to add a feature to a 20 year old codebase.

As personal anecdata, this checks out.

10 years C++, mostly C++11 once it started to exist and be available.

After a few years of Rust on the side, I was x2 to x3 more productive in Rust than in C++.

I regularly think that the way I express code in Rust would be very tedious to do in C++. The ingredients of the magic recipe are:

- Proper sum types (Rust's enum)

- Exhaustive pattern matching, destructuring, the initialization syntax

- The expression-orientedness

Other things that make working with Rust comparatively a joy:

- 99.9% of the time, no need to hunt for UB during reviews

- quality and "standard-ness" of the tooling: rustfmt, rustdoc, clippy, cargo

Rust just hasn't expanded enough yet :)

So we can expect another round of layoffs?