> However a programmer can just as easily set an encryption key to `default()` in Rust and end up with the same issue. It may be "explicit" but programmers get

> However a programmer can just as easily set an encryption key to `default()` in Rust and end up with the same issue. It may be "explicit" but programmers get in habits of using things like `default()` and so it's still as likely to happen as it would with non-explicit defaults IMHO. The point is you don't offer any default if there is no safe default, and so it's not so easy. Yes, a determined programmer can use any API badly. But nudging them in the right direction helps move the needle.