Rust

5989 readers

53 users here now

Welcome to the Rust community! This is a place to discuss about the Rust programming language.

Wormhole

!performance@programming.dev

Credits

The icon is a modified version of the official rust logo (changing the colors to a gradient and black background)

founded 1 year ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

EdTheLegendary@programming.dev

kahnclusions@programming.dev

torcherist@programming.dev

247

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

[–] breadsmasher@lemmy.world 103 points 7 months ago (3 children)

Productivity is so vague though, Id be interested to see what exactly they measured

[–] towerful@programming.dev 135 points 7 months ago (2 children)

Its google, so probably the number of projects launched, never advertised, then abandoned

[–] dustyData@lemmy.world 28 points 7 months ago (2 children)

If that's the measure then I'm more productive than all of Google combined. Nowhere in the definition says the project has to work as intended or even compile.

[–] LeFantome@programming.dev 11 points 7 months ago (2 children)

I know you are joking but needing to compile is probably one of the reasons “teams” are more productive in Rust.

You cannot check something into the build system unless you can build. Once Rust is compiling, you have eliminate scores of problems that may still be in equivalent C++ code.

Rust works to limit the damage one dev can do to the codebase.

[–] sugar_in_your_tea@sh.itjust.works 5 points 7 months ago

I take that as a challenge. :)

But yes, that compiler checks and awesome linter is one of the main reasons I use Rust. I like working with concurrent and parallel code, and Rust makes that really safe.

[–] bluGill@kbin.social 3 points 7 months ago

my python doesn't need to parse to pass cI, at least to long as I don't write tests that run that code section. Checkmate all languages that have to compile. /s

[–] XTL@sopuli.xyz 1 points 7 months ago (1 children)

Maybe that counts technically, but it's just not the same if the project doesn't have a solid user base when it gets killed.

[–] dustyData@lemmy.world 1 points 7 months ago

I am the user base and, despite my best effort, have not yet turned into a liquid. If I kill my project, does it count? Can I be Alphabet now?

[–] ikidd@lemmy.world 19 points 7 months ago

"We're abandoning projects at an unprecedented rate, proving our commitment to the bottom line."

[–] offbyone@reddthat.com 9 points 7 months ago

It seems likely biased as well unfortunately if they let teams decide on their own what to use. I would wager that teams who on their own switched to Rust are probably teams that were already productive.

[–] prettybunnys@sh.itjust.works 2 points 7 months ago

If you ask my last manager it’s “comments on issues”