| As much as I want to like web components, Google's behavior with this new "standard" has been very suspect. The "intent to ship" thread from February this year is something everyone should check out. Here is Maciej Stachowiak's response to Google's irresponsibility on the intent to ship announcement: http://lists.w3.org/Archives/Public/www-style/2014Feb/0103.h... Shoehorning more and much junk into HTML, a markup language with only two types, strings and children, will likely result in bad juju. It may be great for setting things up declaratively, but not for controlling something with state that changes over time. It will serve to reduce what's possible instead of enabling others to explore ideas on the web that are currently only possible in native. What we need is a low-level retain mode scene graph with a JavaScript API. DOM is a pretty inadequate replacement for a real scene graph. DOM is simply too costly to manipulate and re-arrange and I don't see what WebComponents does to fix that problem. This might delay the crisis the web feels relative to native, but will just punt the problem a few years down the road at best. Lastly, some required reading for anyone who wants to educate themselves on the Shadow DOM: http://acko.net/blog/shadow-dom/ |