> As of now, I have still yet to see a JS framework that made any sense to me. The basic issue with the DOM is that it makes state management a pain in the ars

> As of now, I have still yet to see a JS framework that made any sense to me. The basic issue with the DOM is that it makes state management a pain in the arse. So you have written a DOM widget and you want to incorporate it in a bigger widget, so you have to have some kind of "composite" API with a widget life-cycle that pumps data and dumps custom events from/to somewhere. It's not that hard to code, but by the time you are finished coding a library that handles all that you have created you own front-end framework basically. Web Components help a bit by it doesn't seem that Google, Mozilla or Microsoft and co are doing a very good job at promoting them, pushing them in their browsers or even education people about them. It looks like it is one of that spec browser vendors don't like for whatever reason : https://caniuse.com/#search=web%20component https://caniuse.com/#search=web%20component Vue.js actually retains most of the philosophy of Web Components like Polymer so I went with that instead of React,Angular and co. Front-end development is all about state management.