> Which is easier to achieve when languages are strong typed and require explicit escape hatches for doing unsafe things. No disagreement here. What I'm saying

> Which is easier to achieve when languages are strong typed and require explicit escape hatches for doing unsafe things. No disagreement here. What I'm saying is that, in today's environment, requiring escape hatches for dynamic resource management is effectively requiring escape hatches for everything. The worst part is that, in most languages, you don't even need to enable escape hatches to preform nonsensical operations like mutating the same object in two threads, without explicit concurrency control. Literally everything is unsafe! To the best of my knowledge, the only practical language today that attempts to mitigate these issues is Rust. Even if we somehow revived those old "safer than C even if this doesn't mean much" languages, they would probably not help much. > Expensive is relative. I rather have the computer do stuff for me, and focus being productive. With runtime checks, your computer isn't really doing anything for you. Your user's computer is alleviating a problem created by you.