So you learned React. So you added ES6 integration. So you got good at abstracting your code into components. So you…stop. We don’t care.
Just because you learned a solid framework with some good use cases does not make you a genius. And it DEFINITELY does not make React the correct choice for everything you do; in fact, it’s probably not the best choice in the majority of cases.
“Fit no stereotypes. Don’t chase the latest fads. The situation dictates which approach best accomplishes the team’s mission.” Colin Powell
Stop choosing ReactJS for the sake of choosing ReactJS! It is not the one-size-fits-all solution you are using it as. If your site has a dynamic form, you don’t need a freaking virtual DOM. If your app needs simple templating, you don’t need a fire-breathing monster! Young developers in particular are sucked into the coolness of the framework and use…it…for…everything. It’s ridiculous, and ugly. [Side rant] JSX, really? “But you get used to it,” they say. You get used to the taste of mediocrity too, but that doesn’t mean you should keep drinking it.
“Five-Guys bacon-cheeseburgers are amazing, just not for breakfast.” -Me
In the end, the choice is yours, but don’t let your opinions be formed by the fads of the masses. Find out why companies like Google, MSN, and Vevo use Angular. Or why companies like Sony, Reddit, and Pinterest use Backbone. Or why companies like Netflix, Yahoo, and LinkedIn use Ember. There are smart people out there not choosing React. Ask yourself, why not?