You're correct but that's kind-of missing the point: I imagine the parent was trying to say you can have the deterministic management of non-memory resources li

You're correct but that's kind-of missing the point: I imagine the parent was trying to say you can have the deterministic management of non-memory resources like C++, without the downside of loosing memory safety. It's low-signal to say that memory leaks are possible, since, as the article in question demonstrates, it's perfectly possible to get leaks in languages like Java. On `forget`, it's equivalent to the following Python, which can be translated into pretty much any language one wants: holds_reference = [] def forget(x): global holds_references holds_reference.append(x) There are cases where one needs to think about avoiding leaks, but no more than C++.