This is another example of how web development hasn't changed at all from its state in 1996. At least, the part where you need specific code paths for every we

This is another example of how web development hasn't changed at all from its state in 1996. At least, the part where you need specific code paths for every web browser that you want to support. It's sad, really. We've had HTML5 sold as the holy grail where you get to write your code to The Standard and it will work the same everywhere. Except The Standard is open enough to interpretation that no two browsers implement the same thing exactly the same way. And little bugs in one browser's implementation mean you can't rely on individual features, to the point where most features have to be either crossed off your wishlist or worked around. It was the same when the DOM and CSS changes came in around the turn of the century, and all you need do was code to The Standard and everything would work everywhere. (But then Netscape 6 came out and couldn't even render netscape.com anymore.) The saddest part is that this same demo could have been written in Flash (a 15 year old version of it if we wanted), and it would run not only on every major browser in existence, but also faster and smoother by pretty much any benchmark you care to name. Don't get me wrong, I still have my bet squarely on HTML5, and I really really want the browser vendors to get their shiz together. But as a front-end developer I've personally been waiting seventeen years for it. And it seems as far away today as it ever has.