I'm not saying that the author doesn't know what a framework is in general. What I'm saying is that this article can be boiled down to something like: "Javascri

I'm not saying that the author doesn't know what a framework is in general. What I'm saying is that this article can be boiled down to something like: "Javascript has support for feature X, Y and Z, therefore we don't need any frameworks". I should probably also not list Ember's features in my comment, because it's not only about any specific feature - it's also about conventions and app architecture. I think that the underlying concern is valid, ie. we would all be better of if we all joined forces and push for web standards, which can be used in any framework. The problem is that the conclusion, ie. we shouldn't use any frameworks to achieve that, is wrong. Framework authors care about standards and I personally think that each framework will try to adopt more and more native JS and HTML features, but it doesn't mean that we won't be needing frameworks anymore.