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.'
Permalink for comment 485427
To read all comments associated with this story, please click here.
RE: HTML 5 == Pointless Bloat
by Lennie on Wed 17th Aug 2011 00:50 UTC in reply to "HTML 5 == Pointless Bloat"
Lennie
Member since:
2007-09-22

(I will try not to repeat what galvanash already mentioned)

HTML 5 offers little if any improvement


Actually one of the big improvements in HTML5 is that many differences between how browsers parse (mistakes in) HTML should now be handled in the same way.

The scary part is, this means that ALL the progress of HTML 4 Strict and/or XHTML 1.0 Strict is being flushed right down the crapper.


The scary part was that the W3C wanted to make an INcompatible XML-based version of (X)HTML following after (X)HTML4.

That would mean if you would visit a webpage with an older browser you wouldn't see anything useful.

No browser vendor wanted that, so that is one of the many reasons HTML5 or anything really came out of W3C for a long time.

Instead Mozilla and Opera started WHATWG to fix that, later Apple and, in a way, Google joined them.

You figure in the bloat of the pointless allegedly semantic "header, nav" elements that seem to exist ...


The semantic elements exist to make it possible to create alternative layouts easier and to make it possible for other tooling to understand the page. Things like screen readers for blind people.

Some thing actually help reduce the foot print of pages.

That is also one of the reasons we now have a lot of new INPUT-tag-types. To not need extra JavaScript to handle what could easily be handled by the browser. Form validation and so on.

Even if you dislike that other people do add divs with 'nav' and 'header' to their page. Many are doing so. You'll have to agree that having a standard way of doing that can only be an improvement.

Reply Parent Score: 3