« | Blog Home | »

HTML5 : Some Serious Sausage is Getting Made

Project52 : Week 2
File Under: I didn’t need to see the shit squeezed out of the intestines before they are turned into sausage casings…
OR
Fire Under: How did the drafting of the specs for the new HTML5 and web standards turn into a serious detour in to the spider webs of Mirkwood?
Wow! The Twitter-verse erupted this last week on WTF is going on in HTML5 world:

“is there a good concise blog post anywhere explaining just what happened to HTML5 / WHAT WG last week? Seeing the trees, not the forest.” – @mezzoblue

‘Thinking of getting this framed: http://icanhaz.com/specdance” – @adactio

“Pleased that http://whatwg.org/html5 is back to being a spec called HTML5 (and more) rather than HTML (including HTML5). Thank you @hixie.” – @adactio

” ‘#HTML5 is a beautiful mess’: Sitepoint podcast with moi, @lloydi, @cssquirrel. Transcribed as well, thanks @sentience http://bit.ly/5rJmbS” – @brucel

“#html5 punch-up featuring @marcosc, @hixie, @shelleypowers, @johnfoliot http://bit.ly/4Ojp2v” – @brucel

And there are many more Tweets from Jan 8th to 15th on the subject of HTML5, the WC3, WHATWG, and the spec deliberations.
I am unabashedly a fan of strict XHTML 1.0, as I love the element tag minimalism and the strict code typing. If I code a site in XHTML 1.0, be it transitional or strict, I have few worries on what device will the site work on and I have fewer cross-broswer debugging issues than if I write in HTML 4.01 or the like. I realize that others want more features and the early specs of HTML5 appear to make better semantic sense, but the web standard spec and full browser adoption is supposedly years away.
I don’t like to watch the tech sausage being made, I much prefer to let folks duke it out behind some closet doors and then when the browsers adopt the spec, then I will learn it. My passion is in mobile and the web that works for all, not to be the first to use or develop a tecnology. On top of all of that, I am a minimalist. I prefer lean, mean, and elegant over busy, full-featured, and many-optioned.
I first noticed this week’s brouhaha when Dave (@mezzoblue) tweeted his call for someone to interpret and explain the forest for the trees (first tweet quote/link above). Tonight was the first time I had the opportunity to go through my feed reader and read some of the blog posts on the HTML5 rupture of the last 9 days.
I started by reading Dori Smith’s post, My (current) opinions on HTML5, on Backup Brain which was a good summary of the situation and how it effects the various parts of the web design and development ecosystems. Dori is clear sighted in the matter and I noticed quite a few comments, upon clicking on the comments, I was treated to John Foliot’s stident interpretation of Dori’s take on HTML5 and Web Standards.
I clicked over to Mr. Foliot’s web site to find that he was in full defense / offense mode all at once. ((O.o))
Mr. Foliot referred to Andy Clarke’s “Keep calm and carry on (with HTML5)
Faruk AteĊŸ attempts to find the forest for the close examination of the trees in “The Battlefield of HTML5
Bruce Lawson, Ian Lloyd, and Kyle Weems weigh in with a SitePoint podcast on “HTML5 is a (Beautiful) Mess
Mark Pilgrim asserts that nothing has happened other than the HTML5 spec is in the Last Call phase. Mr. Foliot continues his offense/defense bit.
Wow! See what I miss when I am working rather than reading… Wake me up when the spec is ready and the browsers are using it. Then we can slather the HTML5 up in some garlic oil, cook it up on the grill and make some beautiful, accessible web sites and apps.
No Mirkwood spiders, please.