I’ve also heard that unsafe Rust is even more dangerous than C.

Utterly Untrue :
It’s important to understand that unsafe doesn’t turn off the borrow checker or disable any other of Rust’s safety checks: if you use a reference in unsafe code, it will still be checked.

Except RIIR is a meme, not a real thing to be taken seriously.

Removed

The only point I found that falls under “questionable choices” is :

“If you go looking for compression support in Rust, there’s none in the standard library. But you may notice the flate2-rs repo under the official rust-lang GitHub namespace. If you look at its transitive dependencies: flate2-rs depends on (an individual’s) miniz_oxide which depends on (an individual’s) adler that hasn’t been updated in 4 years. 300 lines of code including tests. Why not vendor this code? It’s the habits a small standard library builds that seem to encourage everyone not to.”
“Even official packages may end up depending on external party packages, because the commitment to a small standard library meant omitting stuff like compression, checksums, and common OS paths.”

Which is somewhat valid, but imo it’s really not as big of a deal breaker as they’re trying to make it out to be.

but removing these symbols might make reverse engineering of the binary harder.

That’s the dumbest reasoning ever.

Loving these, the more toolkits like this the better.
Let’s build the Rust ecosystem into the most useful & complete tool in any developers arsenal for all use cases one ever might need.

deleted by creator