We need (at least) ergonomic, explicit handles

The article discusses the concept of ergonomic, explicit handles in Rust programming. It explores the debate around whether users should have to explicitly invoke handle/clone operations or not, highlighting the impact on performance, memory usage, and correctness. The author argues for making it ergonomic to be explicit, emphasizing the importance of visibility in code to avoid surprises and facilitate debugging. The goal is to balance explicitness with ease of use, particularly in low-level applications where handle creation needs to be both ergonomic and visible. The article concludes that while explicit handles should be the initial focus, there may be room for exploring automated solutions in the future.