Linked by snydeq on Tue 16th Aug 2011 16:46 UTC
Web 2.0 InfoWorld's Peter Wayner discusses the 11 hard truths Web developers must accept in making the most of HTML5 -- especially those who are looking to leverage HTML5 in hopes of unseating native apps. 'The truth is, despite its powerful capabilities, HTML5 isn't the solution for every problem. Its additional features are compelling and will help make Web apps formidable competitors for native apps, but security issues, limitations of local data storage, synchonization challenges, and politics should have us all scaling back our expectations for the spec.'
Thread beginning with comment 485444
To read all comments associated with this story, please click here.
Comment by kaiwai
by kaiwai on Wed 17th Aug 2011 02:22 UTC
Member since:

The big problem I have with HTML5 is the attempt to do a whole heap of changes all at once rather than a bit by bit piecemeal approach where the most important (but non-controversial) things can be standardised and deployed straight away and spend more time on the more complex controversial things that don't need immediate deployment.

Take video and audio - that is the the number one reason why most people have Flash installed in the first place, so that they can watch YouTube and other video services. The focus should be on low hanging fruit like that and not marketing HTML5 as some sort of swiss army knife that'll slice, dice and keep the lettuce fresh for up to 5 days.

HTML5 isn't the be all and end all but for a large number of people once those low hanging fruit are addressed the the need to have it installed pretty much evaporates pretty quickly. Does Flash have a place in the future? sure it does but it shouldn't be at the expense where we have advertisers playing obnoxiously flashing videos.

Reply Score: 2

RE: Comment by kaiwai
by galvanash on Wed 17th Aug 2011 03:13 in reply to "Comment by kaiwai"
galvanash Member since:

You are confusing HTML5 the buzzword with HTML5 the markup standard... HTML5 is the "bit by bit" approach. The alternative was XHTML2, which represented massive and fundamentally incompatible changes relative to HTML4.

Reply Parent Score: 2