That's simply incorrect.
What we are doing is elevating memory handling as some special resource.
The lack of destructors or deterministic finalisation causes all kinds of awkward code.
Probably the best feature of C++ is the support for RAII, and the resulting ability to make life-cycle management declarative, or vanish entirely.
Swapping that for GC, is not a good trade off.
Have GC, but enable RAII or be doomed to reinvent it for every application.
Also, if I don't care about memory, why do I have to specify how my gc works as part of deploying my application to the JVM.
Biting the hand that feeds IT
