Jonathan ‘theJPster’ PallantCan’t argue with facts.
Raven Luni@thejpster But google as a whole is counterproductive :p
Tarek Ziadé@thejpster how do you measure productivity though. SLOC? Yeah Rust wins 😂😜
Louis Dureuil@tarek
I'd say you compare the time needed to perform equivalent tasks.
From personal experience, this checks out. I'm x2~x3 more productive in Rust than in C++
Arend van Beelen@lodurel @tarek @thejpster I wonder to what extent bug fixing is counted as part of the productivity? If the Rust teams are more productive *and* the results have fewer bugs, meaning both more stability and lower maintenance costs, that’s especially huge. It’s also an assumption of course, but I think a reasonable one based on the language’s features.
Shawn Willden (@shawnwillden) on X
@MishaalRahman Android's experience with Rust has been excellent. My team built the first major Rust component (keystore), which is a medium-sized component with significant concurrency. We're now three years in and it has been basically flawless.
@arendjr
I don't have representative numbers like Google, but if they're saying 2x I'd say they're only talking about the immediate productivity gains of the initial implementation (+maybe initial review)
Anecdata, but my personal estimate is around x2~x3 initial velocity, converging to an order of magnitude if I factor maintenance. Rust is really good for refactoring code
Filipi Limi@thejpster where can we check out the rest of the talk ?
@morenonatural Rust Nation will post it on YouTube soon