@tess @mcc Older I get, more convinced I become that the "god object" anti-pattern is indicative of languages where the object-creation / management abstraction is too heavyweight.

To make one new Java class for general consumption, I don't just... Make a class. I create a file, and put that file in the right place, and declare its package membership, and create the class, and declare its members, and-and-and-and... IDEs help but it's still actually a lot of lines of code.

Whereas one new function in an existing class is way, way cheaper, and everything that already knows about that class now has access to it.

God objects are indicative, I think, that what the user wants is easy access to a *context,* either static or runtime, for which a class family and object instantiation are a poor substitute.