Most things are cross-cutting concerns. For example, database access and security are issues that entity-specific modules have to deal with, and it's best to sh

Most things are cross-cutting concerns. For example, database access and security are issues that entity-specific modules have to deal with, and it's best to share those features rather than have every entity reinvent it. Early in the GUI days, you had UI components that were pretty independent. But now they are expected to match the look and feel of given OS versions or brands such that they can no longer be truly isolated: they are expected to integrate somewhat with the OS. If people had the guts to live with "ugly", a lot of things could be simplified. I discuss saying "no" to the IT Fashion Show nearby. It may read like a git-off-my-lawn rant, but software could be cheaper if you kick fadsters off your lawn. Beauty ain't free.