The framework discussion and battle is a very interesting one. All of these frameworks approach the same problems differently, and at different times, resulting in performance and api improvements in one place or another.
What if we were to build a library of patterns instead of full frameworks? They would be complex and multi-step, for sure, but we could all bake them into whatever api or performance priority we had for an individual project.
exactly, patterns over frameworks any day :D
then you don't necessary run into issues that you get with frameworks such as major upgrades that also don't support older versions... or no support because the author(s) moved on to the next project, etc
Just because riot is well suited for a TodoMVC example does not make it a framework. It is minimalistic, it does not enforce a code style and it does not really offer much features. That does not make it less interesting
We have to take into account the quality of Angular's documentation in constrast with the hype that surrounds it when considering the upsurge in popularity of the "angular tutorial" keyphrase.