i think this is sort of what @withoutboats often says about ownership and lifetimes, it's not really *just* about low-level issues
-
-
Replying to @steveklabnik @withoutboats
in this case, rust is making my design better and faster
2 replies 1 retweet 10 likes -
Replying to @steveklabnik
Do Rust people measure time spent doing frees? IIRC GC'd langs can be faster than non-GC'd counterparts due to memory mgmt optimizations
5 replies 1 retweet 5 likes -
Replying to @tenderlove @steveklabnik
I think a lot of the performance benefit you get in Rust is from cache locality, which GC languages struggle with.
2 replies 0 retweets 8 likes -
there are just a lot *less* allocations, in Rust than in Java or a dynamic language, regardless of how they're managed
1 reply 1 retweet 6 likes -
Replying to @withoutboats @tenderlove
yup.
@wycats has been talking about this a lot lately2 replies 0 retweets 0 likes -
Go might be an exception since I believe they do more to try to stack allocate values (and in general are doing a lot on GC perf)
2 replies 0 retweets 2 likes -
Replying to @withoutboats @steveklabnik and
My experience trying to write fast Go code is that I had to jump through some undocumented hoops to get it to not do allocs in the hot path
2 replies 1 retweet 3 likes -
Replying to @hdevalence @withoutboats and
with the result that, writing similar types of code as I do in Rust, I have to think about memory a lot more.
1 reply 0 retweets 4 likes -
Replying to @hdevalence @withoutboats and
I think this can be generalized: Go is easier when you're not CPU bound, Rust is easier when you are.
1 reply 0 retweets 2 likes
Linux native threads are decent enough that as long as your CPU ratio is non-trivial, Rust is fine. We found this at @tildeio.
-
-
Replying to @wycats @hdevalence and
My tweet was vague but by "easier" I mean "don't have to think about lifetimes/memory allocation when using Go"
1 reply 0 retweets 0 likes -
Replying to @TedMielczarek @hdevalence and
ime rust lifetimes make concurrency much easier to understand (because lifetime/ownership matters way more when concurrent is in play)
0 replies 0 retweets 2 likes
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.