this post was submitted on 28 Mar 2024
247 points (94.3% liked)

Rust

6024 readers
1 users here now

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

Wormhole

[email protected]

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
Ategon
EdTheLegendary
kahnclusions
torcherist
247
Productivity of Rust teams at Google (programming.dev)
submitted 7 months ago* (last edited 7 months ago) by arendjr to c/rust
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
[–] [email protected] 23 points 7 months ago (2 children)

Rusts ownership model is not just an alternative to garbage collection, it provides much more than that. It's as much about preventing race conditions as it is in making sure that memory (and other resources) get freed up in a timely fashion. Just because Go has GC doesn't mean it provides the same safety guarantees as Rust does. Go's type system is also weaker than Rusts even setting aside the matter of memory management.

[–] [email protected] 5 points 7 months ago (1 children)
  • data races

Rust still can have race conditions

[–] [email protected] 1 points 7 months ago

True, but ownership does eliminate a lot of the possible sources of them.

[–] [email protected] 4 points 7 months ago

Also go is quite a lot slower than rust. It seems fast compared to python or course but it's probably half the speed of Rust.