11 Hard Truths About HTML5
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.'
E-mail Print r 1   54 Comment(s) http://osne.ws/jca
Permalink for comment 485651
To read all comments associated with this story, please click here.
RE[6]: HTML 5 == Pointless Bloat
by Brendan on Wed 17th Aug 2011 23:43 UTC in reply to "RE[5]: HTML 5 == Pointless Bloat"
Brendan
Member since:
2005-11-16

Hi,

Blame Tim Berners-Lee... He invented it and he was heavily opposed to supporting purely presentational markup since day one. The original browser he wrote used the equivalent of a user agent stylesheet to determine how things were displayed (it was not CSS, but it was conceptually the exact same thing).


It was internal, and not something web developers had to care about, and therefore very different to CSS from a web developers perspective (despite being very similar from a web browser's perspective).

HTML, like almost all other successful markup systems that came before it, is founded on the concept of separating presentation from structure and content. This idea is based on decades hard-earned experience. If you want to make a presentational markup system be my guest, but don't try to corrupt HTML into one - it was never meant for that.


I'm not sure which successful markup systems you're referring to. I hope it's not LaTeX (if you've ever tried to use LaTeX to get both HTML and PDF output that looks slightly similar you'll understand why I'd suggest using something else instead).

I don't get your point (or your numbers). I loaded osnews in firebug and I see 5.3KB of css that is used by the site (the rss stylesheet is tiny and is only applicable to rss - it could have been omitted until needed). The actual page content is only 16.5KB. Everything else is javascript, images, or advertising crap and has nothing to do with you argument or mine (and certainly has nothing to do with controlling look or feel).


The web site's main page has changed since I wrote those numbers (3 new articles added, not sure how many removed), and (at the moment) I get 18.7 KiB for content. The CSS has also changed a lot - it was 215 lines (23.3 KiB) and now it's only 77 lines (8.4 KiB). I'm wondering if the OSNews staff have done a few things to reduce the bandwidth.

I don't think it's fair to ignore any of the javascript. I'd argue that HTML has made it difficult for web developers to control presentation, and therefore they're forced to rely on (for e.g.) CSS and javascript and direct DOM manipulation to regain control of presentation, and because the final "HTML + CSS + JavaScript + DOM + whatever is used server-side" quickly becomes an over-complicated mess; web developers use libraries and toolkits to try to cope. All of the javascript used by this site is a symptom of the problem, and therefore shouldn't be ignored.

So your options are either:

1. Have a 5KB stylesheet, loaded once and cached by the browser, that can control presentation of all pages on the site for the entirety of the users visit.

2. Create some kind of crazy markup that incorporates all the styling it does, and then include that markup in the content of every page of the site, bearing in mind that the user will have to download all that markup again for every page load.

Ok. Now try to convince me that option 2 is "efficient". Or maintainable. Or even sane...


Given the choice between "HTML + CSS + DOM + who knows what else" and "a markup language designed for presentation and no need for anything else", I'd choose option 2; because a single 20 KiB page that uses one or 2 languages is much better than a 200 KiB mess that uses many more different languages.

That is leaving out the vast efficiency savings that are available with modern CSS (this site is rather old).


..and ignoring the vast efficiency savings that HTML could have had if modern HTML was designed for presentation.

You can also, get this, create different stylesheets for different uses - alternate layouts, targeting specific devices or usages, etc., all with the same markup. The list of things that make CSS good is a mile long...


So you're suggesting that CSS means things like WML don't have a reason to exist now?

The model I want is where raw content comes from where-ever (e.g. database), something like HTML is used to present that content to visual users, some sort of "Aural Markup Language" is used to present that content to aural users, something like WML is used to present that content to small devices, something else is used to present the content to search engines, etc. Basically, markup languages designed for specific purposes, rather than a horrid mess that tries to cope with everything imaginable at once.

Why don't you actual learn CSS instead of making up stupid arguments against it?


I did learn the basics. I spent hours fighting with it trying to make it work (and mostly failing because it was far from intuitive). The only thing that learning the basics did was increase my desire to replace the entire "web" stack, from HTTP all the way up.

- Brendan

Reply Parent Score: 2