3 ms·

I would go with the idea behind Polymer but probably not Polymer itself. Most of the newer frameworks have some sort of component analog. Angular has directives

I would go with the idea behind Polymer but probably not Polymer itself. Most of the newer frameworks have some sort of component analog. Angular has directives, Ember has components. You can simulate components with Backbone/Marionette. ReactJS is AWESOME and fits right in with the whole component mentality. The project I did with straight Polymer was fun, but I ended up having to scrap it, as the Chrome last month caused blocker issues.

spankalee 12y ago
Angular directives, Ember components, or any other framework's components are not the same as Web Components. The browser doesn't, and won't ever, understand what they are. They have very weak encapsulation unless used solely within a single framework. You can't easily use them across frameworks. The current battle of frameworks has lead to massive fragmentation. Pulling together a React view with an Angular dropdown and an Ember tree view is damn near impossible. Web Components are real elements. You can use them wherever you can use elements - including in all those other frameworks. That's the difference.