It is an option to replace other frameworks - I've built an SPA with it, it was very clean and natural feeling to me.
Building Polymer components is very similar to building Angualar 1.5 `component()`s or react components (or actually any component system for that matter).
New elements are true DOM nodes which is quite an advantage in my opinion.
You can add redux/uniflow on top of that or some vdom lib like preact too if you need that - I wonder what will come out of `lit-html` that is supposed to be vdom alternative.
One interesting thing one should understand that applications view components that are not meant to reusable should NOT use Shadow DOM (just regular DOM)- this way you can use bootstrap or whatever else to provide "traditional" styling of your application.
BTW I think right now Polymer also requires a build process - because 2.0 is written in ES6 so that means building to support older browsers like IE10/11.
Building Polymer components is very similar to building Angualar 1.5 `component()`s or react components (or actually any component system for that matter).
New elements are true DOM nodes which is quite an advantage in my opinion.
You can add redux/uniflow on top of that or some vdom lib like preact too if you need that - I wonder what will come out of `lit-html` that is supposed to be vdom alternative.
One interesting thing one should understand that applications view components that are not meant to reusable should NOT use Shadow DOM (just regular DOM)- this way you can use bootstrap or whatever else to provide "traditional" styling of your application.
BTW I think right now Polymer also requires a build process - because 2.0 is written in ES6 so that means building to support older browsers like IE10/11.