>What's even worse most frameworks are not that extendable without going out of your way when you need some custom functionality. So as soon as your problem bec

>What's even worse most frameworks are not that extendable without going out of your way when you need some custom functionality. So as soon as your problem becomes interesting, and you could really use some help from a framework, it's when they tend to break and you have to work around them... Then you discover the framework designers consider your problem too far from their core target use cases and so show no interest in improving that area of the framework. The community question why on earth you were trying to solve that problem in the framework in the first place, and tell you that obviously you should have used a different framework from the start. Frameworks all target different use cases; often simply the ones the designers happen to have faced over the years. Half the battle in choosing a framework seems to be finding out what those target uses cases actually are - most frameworks seem to think they are good at everything. God forbid your app evolves and changes such that no framework fully supports all your uses any more... (That's not to say frameworks are bad, I just think there's a bit too much religious fervour involved when discussing them.)