Drew Machat / @negativev / alleyinteractive.com
Webpages made up a bunch of small, semantic, and encapsulated building blocks.
<article> <header> <h2>Fancy Post with Slider</h2> <time is="time-ago" datetime="2012-04-01T16:30:00-08:00" format="micro"></time> <author author="author"></author> </header> <carousel images="images"></carousel> <p></p> </article>
<div id="carousel"> <div id="items"> <div id="overflow"> <div class="inner"> <img src="image1.png"> <img src="image2.png"> <img src="image3.png"> </div> </div> </div> </div>
Like everything else relating to browser standards, we have no idea when they will become usable (or how they'll look, or how performant they'll be, or...).
*except styles, for now
Inching closer to being component-centric. 2.0 is an attempt to trim the API and focus the developer experience, while mapping closely to browser API.
1.4.x, 1.5 have a much better component API.
2.0 takes advantage of ES6 and element API to do more things natively