306
you are viewing a single comment's thread
view the rest of the comments
[-] mholiv@lemmy.world 11 points 1 day ago* (last edited 1 day ago)

I mean yah. That’s what it takes. But like when I try to write code around Arc<_> the performance just tanks in highly concurrent work. Maybe it’s an OOP rust skill issue on my end. Lol.

Avoiding this leads, for me at least, to happiness and fearless, performant, concurrent work.

I’m not a huge fan of go-lang but I think they got it right with the don’t communicate by sharing memory thing.

[-] PlexSheep@infosec.pub 1 points 1 day ago

You mean mutex? Arc allows synchronous read only access by multiple threads, so it's not a performance bottleneck. Locking a mutex would be one.

[-] tatterdemalion@programming.dev 4 points 19 hours ago

Arc is not free, and the extra atomic operations + heap allocations can become a bottleneck.

[-] PlexSheep@infosec.pub 1 points 8 hours ago

Oh, I did not know that. Well, it makes sense that it has a heap allocation, as it becomes more or less global. Though not sure why the atomic operations are needed when the value inside is immutable.

[-] Miaou@jlai.lu 1 points 2 hours ago

How can you otherwise keep track of an object's lifetime if copies are made concurrently?

load more comments (1 replies)
load more comments (1 replies)
this post was submitted on 05 Jul 2025
306 points (99.0% liked)

Programmer Humor

24790 readers
237 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 2 years ago
MODERATORS