Explicit abstractions should be the default, I agree, and the descriptions of Rust's tradeoffs and objectives as a programming language resonate with me. Although I think more effort is being spent on frontend Rust than is wise, but maybe it's a necessary pressure to motivate improvements to Rust (?).

All this discussing with yet another set of explicit resource management, and the complexity of drop traits proposed on the follow up post, make me appreciate that I can use automatic resource management languages in all my workflows.

Slowly it feels like we might as well add back all Cyclone features into Rust, and then Rust will lose its initial appeal, crumbling into the same type system complexity that hindered Cyclone adoption.