> Are you seriously calling global mutable state "expert architecture"? Yes. Putting global state in a class and instantiating it once is pretty pointless. It'

> Are you seriously calling global mutable state "expert architecture"? Yes. Putting global state in a class and instantiating it once is pretty pointless. It's a lot of boilerplate and in the end just hides the intention. To the point that programmers confuse themselves about their own assumptions. Leads only to more bugs. Furthermore, global state (as well as global constant data) enjoys the best support for memory management in existence: the linker / process loader. (well-tested, no maintenance overhead)