Why bother with objects and components at all? The purpose of objects is to provide encapsulation and implementation reuse. With code generation, we reuse the requirement or design and not the code. It doesn’t matter if code gets duplicated and spread about because a human won’t be maintaining it. Objects and components are a human artefact for versioning and managing work among developers. They exist to help us humans deal with software complexity. Let’s use computers to deal with software complexity instead.

Object-oriented middle-tiers are generally terrible because they normalise your access to the data you want and create massive inefficiencies. For example, you may only want to access one property of an object but most systems will make you retrieve all the properties of the object in order to avoid an explosion of combinatorics. This creates a massive waste of data access and memory allocations.

Using a computer to search and calculate all the data interdependencies and optimise data access means we can get radically better performance than a hand-crafted object-oriented middle-tier. Worrying about object design is like worrying about which register gets used on a microprocessor!