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

For HTML, the content itself is just data from "somewhere" (typically a database); and the job of a web developer is to design and control the presentation of that content. Idiotic crud like CSS and "semantic" tags (even old stuff, like the "em" tag) just make it harder for web developers to do their job well (as they can't really say how any specific browser might render it), and push developers towards using things like Flash as a way of controlling presentation.

WOW... that's the dumbest thing I've heard in a long time. Lemme guess, ASP developer?

Semantic markup and separation of presentation from content allows you to use less markup in your server side code -- it allows you to reskin the entire page without once touching whats making the markup -- it usually ends up less code overall.

How is that "making developers work harder" -- or are you one of those who's worshiping at the feet of the dipshit photoshop jockeys who think they know ANYTHING about accessibility, maintainability, or even what's practical to implement on a website in the first place?

Your entire post reeks of failing to understand the technologies you're running your mouth about! But then, I could say the same thing about the people who coded the latest iterations of Hotmail, Yahoo's entire site, or Google Search...

Type of statements I'd expect from someone white-space stripping to hide bad coding practices, still using tables for layout, failing to put a doctype on there so it has to hack around IE being in quirks mode, line-breaks instead of paragraphs, non-breaking spaces and line-breaks to do padding's job, tables for NOTHING (worse than for layout!) and inlining ALL their presentation so they can't even leverage caching models across pages.

Much less a lack of headings, lists or anything else to make things like search engines and screen readers treat a page as anything more than one giant run-on paragraph. Author meta after HEAD is closed, multiple instances of closing head and opening body, inlined style attributes, invalid inlined styles... Triple-nested BIG tag doing H1's job... You know, 2.5k doing 1.1k's job?

Edited 2011-08-17 23:22 UTC

Reply Parent Score: 2