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 485664
To read all comments associated with this story, please click here.
Member since:

This is how I interpret the new tags...

NAV = The stuff here consists of primary navigation links. If you are looking for the collection of links that the author identifies as authoritive this website you just found it.

HEADER = The stuff here is NOT part of the primary content of this page, it is decorational and/or contains index/navigation items that are not related to the primary content.

FOOTER = Semantically means exactly the same thing as HEADER, it simply allows for a distinction between things that come before the document and things that come after.

ARTICLE = This stuff here is a self-contained document that is capable of standing on its own. If you want to just grab the meat of this page this is what you want.

ASIDE = Stuff that isn't critical to the rest of the content on the page (like the news sidebar on this site)

SECTION = Arbitrary way to divy things up if you so choose to. I'm not a big fan of this one because it seems to me exactly the same thing as what DIV was supposed to be.

MENU = Everyone thinks menu is a bit "off"... which is why no one supports it. Since no one supports it it probably won't be around much longer (unless someone can think of a way to actually use it effectively)

Anyway, I won't go through them all, because most of the remaining ones are not terribly useful. HTML5 is not perfect - never said it was. I just don't see why you are so hell bent against it. At least some of the semantic tags make a lot of sense - your contention that they all just replicate existing tags doesn't jive for me at all. Sure, you can hack a lot of the existing semantic tags into whatever you want them to mean, but then you have lost their initial meaning. For example, an H1 should be the top level heading in a document - a HEADER of a webpage is something else entirely - HTML5 just makes that distinction explicit.

It brings in new tags primarily to recognize the fact that "documents" that exist outside of the web (which contain their own existing semantic structure) need a way to be incorporated into existing website structure without having to heavily modify either the website or the document. If you don't see the logic in this I don't know what else I can tell you to convince you.

Reply Parent Score: 2