> I think it’s perfectly reasonable to expect “trust me, I know what I’m doing” users to have to step outside of the language to accomplish their goals and use

> I think it’s perfectly reasonable to expect “trust me, I know what I’m doing” users to have to step outside of the language to accomplish their goals and use facilities like inline assembly or implementation extensions. I agree with most of the author's points but this one goes too far. C is the low-level thing you step out into when you're telling the system "trust me" and taking direct control. Asking people to write raw assembly more often instead of using C is a non-starter. I understand the underlying issue with "trust the programmer" (it's too parallel with "unsafe by default") but a more nuanced solution than "make it so C is 100% locked down" is going to be required. Even Rust has `unsafe` and pointer-fiddling utilities (but I don't see how a similar idea would make sense for C).