246

Productivity of Rust teams at Google (programming.dev)

submitted 7 months ago* (last edited 7 months ago) by arendjr@programming.dev to c/rust@programming.dev

124 comments fedilink hide all child comments

Slide with text: “Rust teams at Google are as productive as ones using Go, and more than twice as productive as teams using C++.”

In small print it says the data is collected over 2022 and 2023.

you are viewing a single comment's thread
view the rest of the comments

[-] asdfasdfasdf@lemmy.world 7 points 7 months ago

A lot of it is about moving problems from runtime to compile time. JS, for example, has most problems live in runtime.

Imagine you're hiring an event planner for your wedding. It's an important day, and you want it to go well and focus on the things that matter to you. Would you rather hire an even planner that barely interacts with you up until the wedding because they're so "easy to work with"? Or one that gets a ton of info and meets with you to make sure they can get everything they need as early as possible?

Rust is like the latter. JS is like an even planner who is just lazy and says "we'll cross that bridge when we come to it" all the time.

C++ is like a meth addict.