Why memory safety is becoming a hard requirement

Google published numbers from their Android Rust migration: memory safety vulnerabilities dropped from 223 in 2019 to under 50 in 2024. NSA and CISA have both issued guidance pointing at the same root cause: roughly 70% of exploitable vulnerabilities trace to memory safety bugs. I started using Rust for the k3s-dashboard backend to learn it properly. The practical upside: Axum's type-safe extractors surface K8s API mismatches at compile time rather than in a production alert. It also changes how you write TypeScript. You stop writing catch blocks that swallow errors and call it done.

sources