3 ms·
What's the difference between this and Polymer? It seems to be somewhat similar.
by Mackiovello 10y ago
What's the difference between this and Polymer?
It seems to be somewhat similar.
- pomber 10y agoPolymer adds some syntactic sugar over this. This means that polymer will get faster on WebKit because it won't need the polyfill.
- Fifer82 10y agoI have the same question, and where does either fit into the other bits and pieces like Angular and React?
- Mackiovello 10y agoExactly! It would be interesting to hear what the creators had in mind when they built this.
- tdumitrescu 10y agoMaybe it's not obvious from the WebKit article: Custom Elements aren't new, their native implementation in WebKit is what's being announced here. Custom Elements are part of the Web Components collection of cross-browser standards introduced in 2011 (and still not finalized). React was in its infancy at the time, Angular was just getting off the ground. Polymer has always been built on top of the Web Components standard(s). This post isn't about "Yet another new framework competitor!"
- skybrian 10y agoThe hope is that people will be able to make custom tags that work with any UI framework, so you could use them with Angular or React or no framework at all.
- untog 10y agoFor one, this is integrated into the browser. No dependencies required.
- spankalee 10y agoPolymer just makes it easier to create Custom Elements. It mostly adds templating and data binding, which aren't built-in concepts in the Web Components specs. Every Polymer element is a custom elements, and they can freely mix with other custom elements. Custom Elements and Shadow DOM being implemented native in Safari means that Polymer is just much smaller and faster on Safari.
- tomatsu 10y agoPolymer is an opinionated library for creating Web Components. It comes with the required polyfills to make it work in today's browsers. Performance is better with browsers which support it natively.