Pick a framework for your and the company's future

As a phone/car/.. user, I will like to buy a phone/car/.. that will last for some years. For that, I have two options - just follow what people are buying in general OR fry my brain by googling out the specification of hardware and software so as to analyze the future. With so many opensource frameworks available now, the same question popped in my head as a developer. For that again I had two options - should I do resume driven development OR should I evaluate the business value gained (e.g. in terms of productivity) vs new hot shiny framework (as an early adopter definitely get benefit in the market).

However, there is a little catch, in the case of a phone it is a small amount of money invested but in case of a framework, it is something more precious - your time and organization's money (lots and lots).

How I approached it?

So the problem for me was how to evaluate a framework that will not be knocked out like knockout. So I analyzed the code for a few major frameworks to identify what percentage of the codebase is still present and available for use after 5 years of development for new versions. This can loosely translate into what percentage of what I learned for a specific framework (assuming I learned directly from opensource code) is still of use after 5 years. Thus helping me to focus on learning new capabilities or improvements. I believe this will not only help an individual who is investing time in learning something which is long term but also help the organization that can spend money on solving business problems instead of making me re-learn a syntax.

Comparison Analysis

Let me know if you would like to see any specific frameworks in the graph. (I will keep on updating the graph with other frameworks)