> for a complicated domain object with many other composed objects this starts to be a pain It may be that complicated domain objects with many other composed

> for a complicated domain object with many other composed objects this starts to be a pain It may be that complicated domain objects with many other composed objects are not compatible with this style of programming. Whether or not that's a good thing could be the subject of an interesting discussion. For one thing, negative experiences with the "large complex classes" approach to domain modeling is a major factor in the backlash against object-oriented programming. Lately I've been trying to familiarize myself more with the early literature of OOP, and I'm discovering that even OOP's early pioneers had already had bad experiences with it, and would warn against the temptation to do things that way. OTOH, there's undeniably a certain attractiveness to it, otherwise it wouldn't be so common.