To me this attributes more towards general evolution of the browsers which naturally leads to more complex requirements for the modern web-app. I remember that in 2010, when we started re-writing our desktop apps during our transition to web, the initial requirements were such that it was still possible (although very hacky) to use the latest version of ASP.NET. Then 6 months later we received a new set of requirements which rendered this _latest_ stack useless. We literally had people sleeping under the desks pulling all-nighters trying to transfer a session state between browser and server without dropping an egg. That's was around time when backbone.js came out.

If we compare the things that browsers can do _now_ with what was possible 5y or 10y ago, no wonder why we have so many new frameworks. Browsers are trying to catch up with (or even replace) an OS as a main container for running an application and because it's hard to release all features _at once_ without agreeing on standards, we have a situation when people have to choose a new library each time a new major API/feature is available. And this what I see is the main reason why `front-end development is so unstable`

WebAsm is coming which will again lead to yet another huge re-write.