Not to mention the controversial Encrypted Media Extensions. I'm curious to see who the first to use them will be, and how easy the implementation will be to break.
I like the Template element, but what I'd really like is a way to escape out of JavaScript and html directly to my JavaScript views. That'd be more convenient than splitting client side view development across the JavaScript logic and html templates that reside somewhere else.<p>Plus, I think that'd offer caching benefits vs. having to send templates across the wire every time.
Another article here today pointed me to this: <a href="http://caniuse.com/calc" rel="nofollow">http://caniuse.com/calc</a><p>CSS calc() unprefixed on Chrome 26+
Awesome indeed, the thing that always makes me sad though is that you'll always have that IE 8 user which can't see your website properly, sure, you can use Javascript to make up for it, but it kills the whole emotion of using something awesome.
Templates look nice, but I really wonder how different this technique is from document fragments that one can create using document.createDocumentFragment and other related DOM handling through the convenient JS API.
What's the performance on <template>? This approach seems like it'd be slower than having templates precompiled on the server and already served as JavaScript.