Things are much simpler:

1. Want a bug free code - do bug free code. Spend time carefully evaluating every line and interaction

2. Want third-party code and safety - examine that code in the same way

3. Whatever you do, assume there is a bug in any software you use, so plan and organize accordingly

4. No amount of magic pills can substitute the above. So yeah, it is a skill issue. Also an issue of kids wining that there are bugs and they don’t feel safe, so they want to cling to magic pills instead of dealing with the reality

And while you bring up a “boo-hoo, software written in C has bugs” common knowledge, to my best knowledge standard Rust library still has unsafe parts. But that’s no problem, because contracts, sure. Thanks for demonstrating how full of nonsense you are, bye

More like Rust has rotted someone’s brain. “Hey, I can’t code safely, so I will use this new toy that is supposed to make me”. This line of thought is OK as long as it does not get imposed on anything I do as a programmer