One of the essential problems with any new technology is whether to adopt it and relentlessly abandon users who are not able to upgrade or miss out on new possibilities and eventually become irrelevant. The middle way of course is to fly to the latest technologies as soon as they are stable enough but also provide fallbacks and, where necessary, reduced functionality to users of older systems. This has been the lot of any web developer for years now, where the round blue albatross around everyone necks has been IE6.
Every code path has a cost, and supporting multiple different generations of browser has a high cost (development, testing, support, maintenance, and most importantly coder misery). In recognition of this, one company has even begun passing that cost on to the customers in the shape of a markup for those who use their site with old versions of IE.
Adam Iley in this article apprise that for the customers who are increasingly prepared to upgrade their browsers, his company is preparing newer versions of some of their core libraries that jettison lots of code that only existed to upgrade older browsers as far as possible to HTML5 level capabilities. They are also using the opportunity to allow HTML5 technologies that were necessarily bit players in the past to take center stage.
This post lists down places where HTML5 currently falls short. To read the complete blog visit: http://blog.caplin.com/2012/07/16/the-pain-of-html5/