Item — HN Reader

People who do not want to write safe code will also not use Rust. (Or then use unsafe Rust a lot).

If you want your programmers to write safe code and are in a position to force this, it makes no difference whether you mandate the use of Rust or whether you mandate the use of a safe C subset enforced by a compiler flag.

1 comments

There is an inherent difference between a language where safety is opt-out (safe by default) and opt-in (unsafe by default).

Ignorance or forgetfulness leads to safety by default in Rust. A single failure of vigilance in C leads to the status quo of unsafety.

This is no small difference. If someone doesn't want all the guardrails of Rust, there are still options like Nim and Zig that provide better options than C for greenfield systems projects today.