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

Rust

5957 readers
13 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] 4 points 7 months ago (1 children)

There's nothing wrong with putting Rc<> or Rc<RefCell<>> around data

It's mainly the visual pollution that bothers me. Wrapping everything in the reference counting smart pointers just because you can't be bothered dealing with the borrow checker seems like an antipattern

[–] nous 3 points 7 months ago

I don't know why so many recommend Rc or Arc as a catchall. 90% of the time if you want to avoid the borrow checker then a clone or copy is good enough.