🚀 go-pugleaf

Greg, you addressed this problem at a code level.
Isn't there an architectural solution that might apply to applications
that can be "modularized"?

If a big app has modules which do not share much functionality, isn't
there a way to break it into multiple Java applications so that only one
app has to be in memory at a time?

A quick and dirty way to approach this is an html page that lists the
modules as separate .class's.  Here each module would be in fact a
distinct app.

What if you are writing the app as a Java application, no browser
involved...Is there a way to write a central, parent .class that calls
other .class's in such a way that all the resources of the child app are
released when the user returns to the parent .class?

I've been searching the docs for such a call to an external .class.
Haven't found it yet.

What do you think?  Is this a workable approach?

Thanks.