CSSquirrel A look at web development and web design by Kyle Weems

My grandfather, who unfortunately has been dead for several years, was a man fond of four-letter words to express his sentiments. Once a Navy sailor and a lumberjack, he’d adopted to a picturesque family life a little late in his years. Imagine a charming, smiling old fellow who’d be wearing a nice suit and tie as he shook your hand, then you’d notice “Lloyd” was tattooed on his knuckles. (Hidden under the nice suit was a much larger tattoo of a giant patriotic eagle on his chest.) Midway through a church picnic, he might let slip some colorful language during a tale.

My grandmother did her best to correct his language. One word she’d like to encourage him to use instead was “hooey.”

Today’s comic features hooey. It also features Ian “the Leviathan” Hickson, Google employee and HTML5 editor-for-life (nowadays, he’s more of a generic HTML editor-for-life, which is likely a much sweeter gig) as well as Larry Masinter, Principle Scientist at Adobe.

The hooey in the comic is hyperbole for the effect of comedy; Ian has not outed Larry as a cannibal.

However, Ian did perform some character assassination last Friday when he fired off this blog post accusing Adobe of “blocking” HTML5. He also took the opportunity to simultaneously claim he couldn’t reveal the author of a post for it being in a private list (he chose to use the word “secret”, likely for dramatic effect) while immediately revealing the author’s identity in the very following paragraph (which in this case was Larry.)

There’s a few issues here that point at the continuing mire that is the political process of HTML5, and the resulting decrease in public confidence in the resulting product. First, we’ll look at Ian’s charge: that somehow Adobe is blocking HTML5. This is an absurd statement from Hixie, who’s made it clear that the WHATWG controls HTML5 (in his view) and not the W3C. So for him to claim that a W3C action is impacting the adoption of a spec he adamantly states is in WHATWG’s hand is like saying that the mayor of Osaka, Japan is blocking the Washington state budget from being passed. It’s an act of dishonesty at worst, or emotional manipulation of his readership at best.

(I am not saying the W3C doesn’t have a leadership role in the HTML5 effort. Rather, I’m saying that according to many prior statements by Ian, it doesn’t.)

Regardless, several people caught this “story” and ran with it. Perhaps it’s the Apple/Adobe conflict spawning fanboys and lines drawn in the sand, but a lot of people are willing to demonize Adobe at the drop of a hat. So, rapidly, the word was tweeted throughout the digital realms: Adobe hates HTML. And kicks babies.

I wonder how many of those re-tweeters use Photoshop, Illustrator or Dreamweaver on a regular basis?

Fortunately, some non-partisan cowboys came riding into town and cleared the air with a thoughtful examination on the situation. In particular, I recommend reading Simon St. Laurent’s The Widening HTML5 Chasm and Thom Holwerda’s Teacup, Meet Storm, part IV. Please take the opportunity to peruse their posts for some perspective. Once you’ve received that enlightenment, continue.

Done? Ok. Onwards, then.

Ian Hickson is a Google employee. Which means he’s a smart man. His track record of work speaks to that effect, and it’s worth saying that despite my disagreements with his process, much of HTML5’s good parts have appeared thanks to his efforts as the spec’s editor.

Ian Hickson has a methodology for handling people. It’s documented at his website here. One section on discrediting has some lovely gems that seem to apply to the situation: “Discredit the man who produced the report, off the record.” and “Say that he is harbouring a grudge against your group.”

Also, I’m going to propose that our dear Leviathan has been working on HTML5 for quite some time, and as such has been up to his eyeballs in the process for years. He knows how the process works, clearly, and has historically shown his willingness to ignore said process if that gave him the opportunity to do what he preferred over what the majority desired. (That’s also in his book on handling people: If you don’t agree with a rule you are told to follow, announce your agreement to it in a statement, and in that statement, assert that you intend to follow it in a manner consistent with some other set of rules; or that you will consider certain passages as merely being “advisory”.)

So he’s smart, follows a personal methodology of handling people that involves discrediting them, and he’s familiar with the W3C process. Right?

Very well then. Let me say it: Ian’s insinuations about Adobe were, as my grandmother would say, hooey. Intentional hooey. My grandfather would have used a stronger term. Ian deliberately publicized the identity of someone who posted in a private mailing list (immediately after claiming he could not). He used words like “secret” to provide a sense of conspiracy. He used Adobe as a scape-goat so that we’d all see that HTML5 was being blocked by W3C processes (despite his insistence that the W3C has nothing to do with the actual invention and progression of HTML5).

This is the man who doesn’t like HTML5 politics? This is the man who will be controlling HTML5 all versions of HTML for the remainder of his life?

Well, that’s just splendid.

HTML5 is a mess.

That was a phrase in my Refresh presentation in December, when I was speaking of the dueling organizations jockeying for control of the spec.

At the time of my writing, I did not know how clean it was by comparison to its status today.

Today’s comic features Hixie the Leviathan interrupting a Muppet-show like meeting of the W3C HTML5 group. Blame the parody of Henson’s creations on the commentary of one Mr. Jeremy Keith. Tweets like this are candy for people like me. The comic also features Sam Ruby, John Foliot, Manu Sporny, Jeremy Keith and Bruce Lawson as Muppet parodies.

The fact is that it seems that Ian “Hixie” Hickson, the HTML5 editor, has taken his ball and gone home. He’s started splitting out the HTML5 spec on the W3C side of things into a shredded mess, by his own words with the hope that if the W3C spec becomes a giant mess, people will drift to the WHATWG spec by default. He’s petulantly insisted that microdata (his own creation) is part of HTML despite the recent W3C work that resulted in it being moved out of the spec. He states that the WHATWG spec trumps the W3C spec, so the latter organization has to get over itself and get back with the program. He’s implied that he’d prefer authors (that’s web designers/developers) stop using HTML5 features as much as they have because it’s causing problems. (This further reinforces my belief that Hixie is following an Implementer > Author > User mentality instead of the User > Author > Implementer mentality that HTML was built upon.) He’s made HTML versionless, insisting that HTML5 is a snapshot that he’s already gone past, and is sitting as monarch for life on the continuing evolution of the spec.

All this from a guy who’s catch phrase seems to be “I don’t understand.” Which is, to me, a dangerous trait in a person empowered with absolute rule over the spec.

In short, like Jeremy, I’m frustrated with a lot of the recent HTML-related issues from the front of advocacy. I’ve tried to sell HTML5 (and it’s grab-bag of toys) to co-workers, peers in web design, total strangers, and friends who didn’t escape a conversation early enough. I want to see it used more, so the browsers speed up implementation of juicy features, so I can use it even more excessively, and so on.

But if people don’t even know if HTML5 exists anymore, or the status of the organizations working on it seem to be out of whack, why would they bother using the <video> tag or exploring <canvas>? We need to give people something to work with. Which means we need to not have insane grandstanding by a single individual.

But hey, this is just one squirrel’s view: HTML5 is a mess.

When I constructed a comic last week paying homage to the HTML5 Super Friends, it was not my intent to enter into a dread bargain with the force known as “continuity”, a dark master that requires its fearful slaves to create sequential plots that follow chronologically from one to another. It’s largely been my goal to avoid such, due to the impact it can have on my ability to crack a joke. I could argue that making the HTML5 spec seem humorous is enough of a challenge. Enfolding it in some sort of continuous plot at the same time is an effort that largely exceeds any kick I get out of making funny squirrel drawings.

Nonetheless, by the time this weekend had rolled about, I had been exposed to some commentary about the announcement and concerns the Super Friends had produced, given by one Mr. Ian Hickson, esquire. I largely have told myself that I poke fun at Hixie far too often in proportion to what any man deserves. After all, he is putting a lot of large effort into HTML5, which clearly wouldn’t exist in any usable state yet without that effort. Yet, his commentary seemed so deliciously full of hubris and petulance that I was physically incapable of not dressing him in Lex Luthor’s strange purple jumpsuit and assembling around him a legion of foes for today’s comic (which also features Anne van Kesteren and Michael(TM) Smith).

Here is the deal: By and large, web designers (aka: authors) have been largely skeptical about how well HTML5 is going to meet our needs. This isn’t entirely surprising, as our major exposure to HTML5 has been watching browser vendors and accessibility and/or microformat specialists duke it out over any number of seemingly arbitrary issues. Taken at a distance, or even up close when swallowed whole (have fun with the mailing list if you’re a masochist), it could create the impression that HTML5 is some sort of dark Endorian jungle, filled with hostile ewoks lying in wait for well-meaning designers to walk past, oblivious of their gruesome fate.

What the HTML5 Super Friends did, with a very public, non-mailing list announcement about their perusal and acceptance of HTML5, is create a sense that all will be well for designers as HTML5 slips closer to the (possibly too soon) date for Last Call. When Jeffrey Zeldman, Eric Meyer, and every other notable name on their list, said “Hey, HTML5 is cool, come on in the water,” they started a large ripple through the design-o-sphere that is bound to be felt very sharply in the dwindling days remaining in this year. What helped that ripple wasn’t just a blanket statement of “It’s all good,” because that would be a lie, and most of us are smart enough to know it.

Rather, they exposed their concerns, in plain language. They then said, despite these differences, which we hope are addressed, we still like what we see.

Call me a sheep if it helps you feel better about yourself, but that sort of critical support for HTML5 has greatly increased my own comfort with the spec as it solidifies.

So, when Ian Hickson, HTML5 editor, gets his knickers bunched up in a fit because the Super Friends decided to do a posting on their various sites/blogs/whatevers about the topic first, then in due process submit their concerns “formally” to the WHATWG mailing list… I can’t help but find the words “petty” or “egotistical” floating to the front of my mind.

To answer your questions, Ian: Yes, the WHATWG’s public mailing list is in fact public. However, it is not nearly as public to the target audience of the Super Friends’ efforts (aka: web designers) as their very blogs/feeds/etc. They are engaging in the process of getting buy-in from designers, which HTML5 has been slow on, rather than the WHATWG, which I will wager is already really well sold on this whole HTML5 doohicky. There is no shame delivered, nor insult intended, by their actions in publicly (and in their own preferred fashion) declaring that HTML5 is good, but could use some tweaking.

So, good sir, I recommend you calm down, take a deep breath, and stop being snippy about the spec every time there’s a public or private discussion of HTML5 that did not directly involve yourself. We’re all painfully aware at this point that the spec won’t change without our power-invested Leviathan’s approval.

Sooner or later HTML5 will not be the most interesting topic to wax poetic about. This is not that day.

I’m usually in sync with the web-related posts written by Jeremy Keith over at his personal site, Adactio. He’s usually saying something I’m thinking (albeit with more eloquence than I could muster), or spouts some gem of wisdom that I wish I’d thought of first. As such, it is safe to say that I respect him and, normally, his opinion.

This weekend, however, he wrote firmly on the topic of HTML5 and its process, in The HTML5 Equilibrium. In doing so, he made a sort of sandwich. The opening and closing of his post were two delicious, carefully toasted buns of high quality. But firmly settled in between them was a rank egg salad segment where he detailed his view on the W3C/WHAT WG “split personality”, ruining my appetite for his creation.

I’ve never been able to stomach egg salad sandwiches.

My reaction was spawned by his discussion of the status of Ian “Hixie” Hickson as the dictator-for-life of HTML5, sitting astride a position of absolute power in how the spec is edited. As readers probably know by now, there’s been plenty of friction lately between the HTML5 efforts and every other W3C group known to man as Ian’s been refuting their expert advice in exchange for his own pseudo-expert opinion on a wide range of topics.

Keith comes to Hixie’s defense by stating that although an unelected autocrat is horrible, it can work quite well. He evokes the power of dictatorship by referencing Thomas Hobbes’ Leviathan and quoting Shakespeare’s Henry V. Specifically, he states that by doing so we transfer “moral responsibility” from the populace to the dictator, then goes on to say that Ian has taken this mantle and used it evenhandedly and fairly.

In short, Jeremy uncouples the means from the ends. Leviathan, written in the 17th century, is a text that firmly opposes Separation of Powers and refutes the Right of Rebellion, claims the sovereign’s acts are incapable of being considered unjust, and makes it unjust for the populace to attempt to unseat the sovereign.

In short, do what you’d like, Hixie. It won’t be our fault, because we’ve given you all the power, and from here on out we’re blameless. But at the same time, should we disagree with you, tough for us. It’s all your show now.

And really, that’s what it’s become. The Hixie Show. The amount of “not invented here” mentality that evades the modern HTML5 spec is odious. Accessibility in HTML5 isn’t being decided by experts. Process, when challenged through W3C guidelines, is defended as being “not like the old ways”, in essence slapping the W3C in the face. Ian’s made it clear he won’t play by the rules. When well-meaning experts carefully announce their opposing positions and desire for some form of closing the gaps, Ian and the inner circle constantly express how they don’t understand. This understanding issue has reached a comedic point. When Sam Ruby pressed them on the subject during an objection by John Foliot (as noted here), Ian’s response is a glib “I don’t understand John’s concerns. He hasn’t explained them. He has just made unsubstantiated demands.”

This phrase (“I don’t understand”) is used by Ian so frequently that I’m genuinely concerned. He’s ostensibly a bright man. The usual objections and positions by other parties in the HTML5 dialogue are incredibly well documented at this point, in staggering detail. To claim the inability to understand exhibits one of two traits: Either Ian is a simpleton, or he is deliberately “misunderstanding”.

I don’t think it’s the former. Ian has clearly demonstrated his phenomenal intelligence. Yet, the latter option is part of Ian’s well documented deny, delay, too late methodology for handling people. Engaging in this sort of behavior is disrespectful of his community of peers, and more than discouraging when its coming from our empowered Leviathan.

We must accept this, though. Because it’s the results that matter, right? If we get a HTML5 spec, any HTML5 spec, we should be happy about it. Despite all the assurances to the contrary, I can’t really believe that it’s acceptable to consider a product’s method of construction to be independent from its quality. If so, I should be paying far less for my garments, right?

There’s a thought process here that is so far removed from the 21st century as to be terrifying.

In today’s comic, Jeremy Keith reveals the Leviathan to the Squirrel. Things go badly. But remember, it’s only the Leviathan’s fault, because we’ve absolved ourselves of both power and responsibility.

Right?