They actually should. As such a rewrite went so well for sudo-rs.
The article mentions 100% code coverage with tests as one of requirements from their users, and having "safe languages" emit defensive asserts and checks when compiling correct code means 100% branch coverage is impossible. How do you propose to address it with rust?
What
It's either trolling or sarcasm. May be both.
Not trolling. Everyone knows C is not safe.
C is safe if you know how to write it. Jokes aside yes you need to be more careful.
Life as a whole is not safe, and not everyone seems to be aware of this.