I'm not the downvoter. The process you described is part of the due diligence you go through - checking for activity, longevity etc. You described a good starti

I'm not the downvoter. The process you described is part of the due diligence you go through - checking for activity, longevity etc. You described a good starting point for evaluating a framework (I don't think you should have been down voted for that). Unfortunately, that's not the end of it. As with your Closure example, it's not easy to see the issues until you're up in your neck in them. At that point you have a revelation about how truly borked you are, struggling to make progress when you've gone too far to go back. That's why it makes sense to experiment a bit to see how it feels. That's not something easily quantifiable. If it were quantifiable then there would be no need for these discussions at all. There would only be one framework in any space worth looking at because it would have the best number against it. Unfortunately, in the case of application frameworks, building something small is never going to be enough.