Return to Answer

One thing that unifies them is that they all let you create an architecture free of cycles that still manages to effectively communicate. This helps ensure a code change hits a firewall soon rather than spreading through the code base breaking component after component.

In this particular case it would give you the flexibility that comes from expressing only your real needs that the framework fulfills thus making life easier on those who come later to replace the framework or repair it when it experiences a breaking change. If you don't care about any of that now nothing can make this worthwhile. Just call it "technical debt" and move on.

In this particular case it would give you the flexibility that comes from expressing only your real needs that the framework fulfills thus making life easier for those who come later to replace the framework or repair it when it experiences a breaking change. If you don't care about any of that now nothing can make this worthwhile. Just call it "technical debt" and move on.

I've talked about this before and created this handy little animated gif to show the flow of control:

I've talked about this before and created this animated gif to show the flow of control: