On the contrary; Rails was a massive innovation because it proved that opinionated, reasonable defaults ("convention over configuration") is how most people actually want to write software. For a CRUD app, Rails was a shining beacon of light, because it allowed you to crank one out in mere hours, instead of days of fiddling with repetitive glue code that you would've had to write instead in literally any other web framework of your choice. It meant average coders could be productive instead of overwhelmed, and competent coders could move on to different projects faster.

The GP post has a point. Almost every MV* JS framework starts from scratch because they all believe their slight variation of the paradigm is better than everyone else's, but the greater scheme of things they are more similar than different. When one comes out with a framework that in earnest changes how JS development is done -- and achieves some staying power -- things will be different from the myriad of near-equivalent-but-totally-incompatible choices.