🚀 go-pugleaf

I believe you are both correct.

Most created objects can be managed with explicit creation/destruction code,
placed in abstract data type specifications or otherwise part of the
application, because their lifetimes are naturally connected to the algorithms
(or messages) that use them.  Sometimes, however, dynamic reclamation (garbage
collection) is truly necessary (to avoid unnaturalness or inefficiency).  A
useful parallel is the need for both stack and heap data storage in
general-purpose programming languages.

When an application can use explicit creation and destruction for most of its
object management, the garbage collection overhead is reduced, and this has
all sorts of good consequences.

David Spector
Prime Computer, Inc.
ds@primerd.prime.com  (until my layoff, expected soon)