Hacker News Reader

> obsessed with ownership, may give rise to whole new classes of errors that otherwise won't be there

How does baking the ability to statically determine resource ownership into a language lead to a class of errors? What sort of errors are these?

View on HN

By taking away the ability of programmer to read and understand the code written by somebody else, or by himself 1 week ago

I have no clue what you are talking about and I don't think that you have either so I'll just leave this discussion now.

As someone who has written many thousands of lines of production Rust code, this doesn't ring true to me at all. Ownership semantics have dramatically improved my ability to reason about my code, not the opposite.

Reply on news.ycombinator.com