I think alot of the devs today have grown up with all this frameworks on top of other frameworks. The problem is you lose power with every layer of abstraction

I think alot of the devs today have grown up with all this frameworks on top of other frameworks. The problem is you lose power with every layer of abstraction. It's the price you pay for it. They also abstract at too low a level, especially since browsers have caught up. They don't need provide a new custom ajax for instance, XHR as implemented in the browser works quite well without imposing an arbitrary syntax on top. So I think people have moved increasingly to vanilla. We've come full circle with the opinionated frameworks and some people are frustrated and where do we go now? Web components are the most promising development, because the preferred approach in sw development has always been isolation/separation of concerns. This is pretty much the opposite of the JQuery style. In theory you can separate using JQuery but in practice still in 2014 you cannot look at source in any moderately complex web app and understand what's going on. Ultimately, its going to have to be a DOM/JS mix (Those aren't going away for a long time) but they never got it quite right. The web component frameworks are the best thing going for the future. IMO they should be declarative, that is - in the HTML - but programmable, and that's the way things have been heading. So in 10 years we'll still have the DOM and JS (although it would be interesting to have more languages easily usable in the browser). As Polymer evolves it (or some equivalent) will make it into the browser.