10 ms·
When you've worked with languages that help you think about ownership (like Rust or even modern C++), being back to languages that throw you a pointer/reference
by lultimouomo 11y ago
When you've worked with languages that help you think about ownership (like Rust or even modern C++), being back to languages that throw you a pointer/reference had leave you on your own to figure out what it's lifecycle is and what you can to with them is a huge step back. For me is the think that sucks most when programming in Java, for instance.
- wtetzner 11y agoJust out of curiosity, why do you care so much about the lifecycle of an object. I can see why you might want to know in the case where you're representing an external resource, e.g. an open file, but otherwise, I don't see any reason to care about it. In face, with persistent data structures, you can't know. The same is true of share (immutable) data with multiple threads. You can't know the lifetime.