3 ms·
We aren't really disagreeing. Forcing Rust into a domain where a GC'd language is more than enough offers absolutely zero advantages (yes, you'll have no memor
by qsort 3y ago
We aren't really disagreeing.
Forcing Rust into a domain where a GC'd language is more than enough offers absolutely zero advantages (yes, you'll have no memory safety issues, but neither you would have had you used Python or Java or Go or whatever), and it's the kind of obnoxious overzealousness that I'm denouncing.
If you're using Rust to write web services you're just wasting your time, I agree with that.
But if the alternative would be C or C++, Rust is at least worth consideration. Ironically, those are domains where you'll have to use a lot of unsafe and/or limit yourself to a subset of Rust, but it's still a nice incremental improvement.
- usrbinbash 3y ago> Forcing Rust into a domain where a GC'd language is more than enough offers absolutely zero advantages (yes, you'll have no memory safety issues, but neither you would have had you used Python or Java or Go or whatever), and it's the kind of obnoxious overzealousness that I'm denouncing. It is refreshing to see that other people share this point of view. I guess we are not disagreeing after all.
- baq 3y agoIt’s sad that it’s refreshing to see engineers doing engineering instead of bikeshedding…
- pornel 3y agoI’d love to have thread safety (Send/Sync) even in GC languages. There are lots of programs where Rust isn’t necessary, but it still has a bunch nice-to-haves besides memory management.