2 ms·
Wouldn't this simply be a situation where you are not checking for nil? I think the more nefarious situation is when a library deep down decides to panic on yo
by imetatroll 3y ago
Wouldn't this simply be a situation where you are not checking for nil?
I think the more nefarious situation is when a library deep down decides to panic on you.
- omginternets 3y agoI mean, Rust libraries can use `unsafe`... You might (rightly!) respond that you can exclude dependencies that use `unsafe`, but then you've just displaced the problem to "now I need to find new libraries". Point being, it's going to be a schlep either way. There will always be a schlep. Which schleps you want to deal with, and how you want to deal them is the trade-off space that different programming languages position themselves within. As I said in another comment, Rust is great, but there's a reason it's not universal. That reason is not that people are ignorant, stupid or lack the incentive to avoid schlep. It is instead that sometimes, dealing with Rust is harder than dealing with the rest of the damn problem. In my case, I have noticed that Go is a good solution when Rust is not. I now have two arrows in my quiver. Neither is my favorite. I think this is the right attitude, personally.