2 ms·
In my experience, OOP works great until you run into a problem domain with circularly-dependent types that actually make sense as such to the business. Certainl
by bob1029 5y ago
In my experience, OOP works great until you run into a problem domain with circularly-dependent types that actually make sense as such to the business. Certainly, there are ways to manage this within the realm of OOP, but I strongly argue that these solutions are half-assed at best.
Also, nesting of complex types (i.e. making assumptions about the shape of the domain model) also seems to be a large part of what causes pain in larger code bases.
> Most programmers I have met in person tend to divide the world thus:
> Wacky research stuff. Unproven, Scary, Unmaintainable.
For us, the "Wacky research stuff" is how we finally solved many frustrations we had with implementing software against our particular business. A relational/functional hybrid model (implemented using C#8 & SQL) has proven to be far superior to any other approach we have taken over the last 6 years. But, we still do OOP in other places where it still makes sense to do so.
- cout 5y agoEven the most fundamental types in smalltalk derivatives are circularly defined (using Ruby as an example: Object is an instance of Class, and Class inherits from Object). Circularity doesn't make this any less useful as a model, just more difficult to reason about. It's a tradeoff.
- ProfHewitt 5y agoAxiomatization up to a unique isomorphism is the way out of the circularity. Actors have been automatized up to a unique isomorphism. See the following: * https://papers.ssrn.com/abstract=3603021 https://papers.ssrn.com/abstract=3603021 * https://papers.ssrn.com/abstract=3418003 https://papers.ssrn.com/abstract=3418003