Posts Tagged ‘justin mcdowell’

The Egotistical Puppet King & I

Tuesday, May 15th, 2012
CSSquirrel #93: The Egotistical Puppet King and I

In a way I should be grateful to Ian “Hixie” Hickson for being an egotistical tyrant. Without his inability to acknowledge that a consensus-driven, well-crafted and usable solution built by a group of well-meaning, hard-working people could actually somehow be better than his own personal opinion, he’s pulled me out of my long-hiatus and back to to the drawing board.

Today’s comic is in fact three comics. No single idea could encompass everything. In all three Hixie gets top billing as the editor-for-life of HTML’s “living spec”. The first comic features Naepalm, chinchilla alter ego of fellow Mindflier Janae Wiedmaier. The second one includes the irreplaceable Justin McDowell. Lastly we see Matt May, Dylan Wilbanks and Ethan Marcotte joining forces with the Squirrel in a bid to take down the HTML king.

(Today’s comics as per usual aren’t meant to imply that the people represented therein endorse my views. I’m saying it outright today because I’m feeling particularly vitriolic and don’t want my words to reflect on them.)

The Situation

For those of you just tuning in, today’s outrage focuses around Hixie’s decision to adopt a problematic, late-arriving, Apple-proposed attribute of the <img> tag into the HTML standard as the solution to the adaptive images issue. In the process he again reinforces his inability to heed the creed of HTML’s priority of constituencies (end users over authors over implementers) while also tossing away the hard work of a community group of developers that built a very functional, very usable solution to that problem in the form of the <picture> element.

If you’d like a summary, you can check out the aptly titled WTFWG by Tim Kadlec, or take a look at Zeldman’s take on the situation over here, which links into an A List Apart article by Mat Marquis on the topic.

I wish this was a new situation. Or that it was surprising. Or that I didn’t feel like I was repeating myself each time I mention Hixie in blog or comic form. The fact is that as the Editor of HTML, Ian keeps doing this. And we keep letting him.

The Puppet

At one point I attributed this issue solely to his gigantic ego and clearly overwhelming case of not invented here syndrome. Now I’m frankly convinced that although these qualities contribute to the problem, the real issue is that he’s the puppet of the browser vendors, namely the three most involved in WHATWG: Apple, Opera, and Google. Although the priority of constituencies dictates that implementers (aka, browser vendors) should be lower priority than developers (who are in turn answerable to end users), it seems that without fail Hixie will bow to the vendors before considering any work on the part of developers at a solution, no matter how reasonable, well-built and documented that solution is.

That’s not a kind accusation, that a man is a puppet. But clearly every attempt to work with the WHATWG has always resulted in developers being treated as second-class citizens to the browser makers. And let’s make it clear: this is our job. We make websites for a living, and the tom-foolery that Ian is engaged in is directly impacting our present and future workflow. We work on making websites every damn day. We know what works for us, and what doesn’t.

And he doesn’t care in the slightest.

“Work With Us”

At this point, Hixie and his backers are relying on the same smoke and mirrors to distract people. Present use cases. Keep engaged with the WHATWG and let them know your technical objections. Get involved in their IRC. But the fact is we as developers have done this over and over and over. Yet at the end of the day, regardless of the hard work put in and all the proof jammed into the pudding, it all amounts to naught. Hixie spends twelve seconds coming up with his own solution or takes what the browser makers gives him and uses that instead.

It happened with metadata. It happened with the <time> element. It’s happening now with responsive images.

The fact is that Ian doesn’t give a shit.

He’s going to do it his way, or failing that he will do what Google and the other browser makers in the WHATWG tell him to do. He’s not going to look at what the developers have built and give that solution a thumbs-up. As John Foliot said: “Dev community, if you continue to author to the WHAT WG doc, you lend your tacit support to heir hixie. Look where that gets you.”

Enough Is Enough

Being part of their process is being part of the problem. I’ve never seen things resolved by following the WHATWG’s “process”, as it amounts to little more than distracting developers while he goes off and implements a less functional, more complex solution to the problem.

Don’t deal with Hixie. Don’t deal with the WHATWG. Directly object to the browser vendors. “Occupy” HTML by making use of the consensus-built techniques that already have functional polyfills. Do what makes sense, and what works for you.Sooner or later, the browser vendors will be tired of the grief sent their way and tell Hixie to roll over.

<time> wasn’t fixed because we followed the WHATWG’s process.

I’m going to say it: I don’t believe that WHATWG is part of the solution anymore. As I’ve been told by others, democracy isn’t always the best approach. Sure, ok. But so far when it comes to the community-build, consensus-driven approach and Hixie’s brain, the community’s solution has proven more effective more often.

I’m going with the community, not the puppet.

Comic Update: Tubes

Tuesday, October 12th, 2010

Today’s comic features Justin McDowell (web designer and founder of Ignite Lincoln) and the Squirrel dealing with the decidedly first world problem of a slow broadband connection while discussing Chilean miners. In short, it’s all about tubes.

I’m claustrophobic to an incredible degree, a trait I attribute to my lifelong battle with asthma and my general impression that smaller spaces contain less air. I cannot fathom what spending over two months trapped a half-mile underground in a collapsed mine must be like. It’s amazing that the men involved have held together as well as they have, and almost as incredible is everything that’s been delivered safely to them through a four-inch wide, half-mile long tube. Sandwiches, drinks, videos, clothing, books.

The fact that they’re about to be winched upwards to the surface world says something about how humans can come together in such trying times to accomplish something so incredibly difficult.

It’s entirely trite to compare such a feat to broadband Internet access. But I’m going there, because I’m a classy guy. Both my home connection and that of my workplace go through Comcast. Over the past week, both locations have had service levels I could compare to my 1995 dial-up connection when I’d log in to play Ultima Online or spend fifteen minutes downloading one naughty photo. What I’m trying to say is that hand-delivering the packets of information would result in a faster speed than what I’m currently experiencing.

What drives me crazy about such things is that for all extents and purposes, this is exactly what Comcast promises. Any of their service packages guarantee up to a maximum level of service, but not a minimum.

I’d like to repeat that. I pay them good money to guarantee that they won’t exceed a level of service, but they can fall as short of that as they please. I wonder how well that would work for other business models. Buy up to a whole hamburger… but maybe you’ll get just the bun. Buy up to a whole website… but maybe you’ll just get a half-finished splash page.

It’s a classic old gem at this point, but I think Penny Arcade’s treatment of the topic goes straight to the point of how I’d prefer to pay such a variable service.

The overall poor quality of American broadband access in comparison to other first-world nations is something I could rant about for hours. Instead I’ll get over myself, link you this hilarious hat picture of Justin I found while getting reference photos of him for the comic, and wish the miners all the best luck in the final hours of their ordeal. ┬íVive Chile!