Debate

Probably most of us still believe that in some time frame for some classes of application HTML5 does indeed offer the prospect and indeed does already provide a good answer to some clearly scoped and limited application use cases.
But in the light of over a year’s experience, some are saying that it’s not yet lived up to its promise and that although like the proverbial Chinese meal they felt full at the time, their hunger hasn’t been satisfied in the medium term and are sceptical about the long term. Perhaps, like other famous cross-device solutions both its promise and its readiness for market were over-stated. Insufficient specification, incomplete feature readiness, inconsistent order of implementation makes this an engineering bouillabaisse and does not provide the sort of commercial respite we were looking for.
So, reality has crept in, today HTML5 does not provide the ingredients for the kind of Michelin dining experience that is often needed. Instead, if you want a TV dinner, then it provides a Pot Noodles experience for consumption on the couch.
So this year, our motion is:
HTML5, far from being part of Gordon Ramsay’s larder is more likely to be used by Stavros at the corner chippie. Fine if you want chips. Do you aspire to be Gordon or are you content to be Stavros?