Food for Thought on Customization

Read this post just now. Points to ponder:

Somewhere in all of this there's a balance to be struck. I don't figure any single framework or whatever could be the solution to all problems. There will be some things it can do which save you money but once you're outside of its sweet spot I suspect any cost savings evaporate pretty quickly.

And if that's the case, what does that mean for the long term life of a system? What amount of change can we expect to see? Might it not need reworking on top of a new framework to suit some new need? Or perhaps we have to take a modular approach and build new functionality separately on top of a new framework and integrate it with the old system? What does all of that mean for architecture?

We probably want to think it over on how to integrate with other frameworks, not necessarily assuming them underneath the wings of Cornerstone, which has been our approach, because it might just be true that I don't figure any single framework or whatever could be the solution to all problems.