Innovation is good. I think the knock against "a new JavaScript framework every other week" stems from seeing JavaScript tools, frameworks, and libraries throw

Innovation is good. I think the knock against "a new JavaScript framework every other week" stems from seeing JavaScript tools, frameworks, and libraries throwing aside 60-70 years of solid design patterns and architectural principles in favor of "minimum viable product" in order to be "first to market." This has resulted in a plethora of relatively immature tools and frameworks that are just better enough than the previous generation of tools to warrant using, but use of the new tools and frameworks to engineer quality software also results in a lot of frustration. For an exercise in what I describe above, try taking an existing AngularJS (v1.x) application, add some non-AngularJS components using ES6, then attempt to generate a comprehensive test coverage report over all of the components in a single testing pass using Gulp, Webpack 2, and Karma. Bonus points if you figure out where to add Istanbul correctly on the first pass through it.