| > Refuse to take jobs Well, I'm unfortunately not in a place where doing so makes sense. Unless you mean only auditing Rust code. > nag managers I already do so. This doesn't change much. There are still too many must-be-evolved C++ projects (no easy incremental rewrite path forward), it is impractical to have engs put significant effort into rewriting in Rust. It's really difficult to convince someone to fix something ain't broken. People coding in C++ are just as desperate as you, that's why someone bring up Carbon [1], a half-baked experimental project to the world last year, instead of just using Rust. Sure, they would like to use a memory safe language as possible. No, they still have to get their job done. > refuse to by hardware that only supports C If it supports C, we can make it support Rust, it's a very fun weekend project to bring-up some nostd Rust code on it. [1] https://github.com/carbon-language/carbon-lang |