They are working hand-in-hand with the spec to ensure compatibility when it's done.

He has over

This tutorial covers most of the topics required for a basic understanding of Polymer.js and to get a feel of how it works.This Polymer.js course also includes templating and styling support to … In the meantime, in order to fill the gap, Polymer suggests the use of polyfills (downloadable JavaScript code which provides features that are not yet built into today’s browsers).

Perhaps most notably, Polymer requires a fairly significant level of expertise in using browser technologies like the DOM. I can't really see why you would not support a polyfill for such things, and it's just ridiculous to assert that component developers thought javascript was going away.

Even when the downloading is complete, you still often have a blank screen for a few seconds. And the question is: Is it yet ready for prime time?

jQuery existed to fill in the gaps between browsers. If a moderately complex website needs some custom elements plain HTML+CSS+JS is a good choice (eg: Bootstrap tabs and accordions) and JS plugins are good enough (eg: jQuery UI sliders as input elements).

In either case shadow dom is a proven way to improve performance whether it's a library of components or browsers in the future. Polymer purports itself as taking a sort of back-to-nature approach that “puts elements back at the center of web development”. Bower already added dependency resolution, packaging and distribution and you can start a private registry faster than you can say bowerbird. great... Added more content to already confused developers... Polymer tutorial & example https://www.youtube.com/watch?v=QbcHYs-OReY#t=33.

http://www.polymer-project.org/docs/polymer/databinding-advanced.html#how-data-binding-works One additional thing is that