How to know the JavaScript frameworks to use

On the 3rd of January 2017, Laurie Voss, co-founder and COO, npm, Inc. released the state of JavaScript frameworks.  On the post, they made it clear that It’s not their intention to suggest that everyone should always use the most popular framework. “There are many metrics to help you decide which one to use, and frameworks vary enormously in scope and application. A framework that closely matches your specific application may not even be mentioned in this analysis but will still be the perfect framework for you.” That is almost the summary of the post. The thing that you should be looking at now is the many metrics that can help you decide the JavaScript framework to use. The post went ahead to explain why the popularity of the JavaScript frameworks does matter. The framework with larger community is easier to get help whenever you got stuck at some point.

npm uses the number of downloads to determine the growth of javascript frameworks. according to them, “You can use npm’s download statistics to give you insight into the number of people actively invested in using and maintaining a package. However, probably more important than absolute popularity is growth.”

JavaScript Front-End Frameworks

From the analysis on the graph above, obvious is the massive growth in React. Introduced in March of 2013 by Facebook, React has been adopted very rapidly. Part of this is a reflection of its nature; unlike some of the other frameworks in this analysis, React isn’t a full end-to-end solution for building a web application. It’s a well-designed solution to a specific need that many applications have, and it incorporates easily with a number of alternative solutions for other parts of the application. Because of this modular nature, React has spawned a whole ecosystem of related packages that solve the problems of the other parts of an application.

That React is growing faster than other frameworks doesn’t mean that you should go for it. You just need to know what the nature of the project you have at hand and go for the right framework for it. Another thing you need to consider is whether the framework can be depended upon to stick around. For example, Angular is getting its continuous backing from Google while React is getting from Facebook. It means that you don’t have to worry whether they would still be in use in the next couple of years.

That’s it. Know the nature of your project. You can read the full post on npm.  Link: The State of JavaScript Frameworks 

There you will see a short and concise review of each framework. You will also see enough graph graphs that I believe would explain better.

You may also wish to read:

Thank you


Kingsley Author


Leave a Reply

Your email address will not be published. Required fields are marked *