Off With Their Heads: Disband the W3C?
Just a few days ago, Matthew Butterick presented a talk entited "The Bomb in the Garden" at TYPO in San Francisco (poor title timing given recent events in Boston). In it, he concludes "the misery exists because of the W3C—the World Wide Web Consortium... So, respectfully, but quite seriously, I suggest: let’s Disband the W3C". Ultimately he suggests that "...the alternative is a web that’s organized entirely as a set of open-source software projects.
In his recent talk/post, Matthew Butterick raises several points:
- It takes a really long time for standards to reach Recommendation Status ("the Web is 20 years old)
- The W3C doesn't enforce standards
- Browser vendors eventually implement the same standards differently
- We fill pages with hacks and black magic to make it work
- Ultimately, what we wind up with still isn't nearly good enough
- There is no good revenue model
- Newspaper and magazine sites all look roughly the same and are somewhat 'low design'.
His presentation is definitely interesting and worth a read/view. In general, if you have been working on the Web a long time, you will probably experience at least some moments where you can completely relate to what he is saying.
Still, it seems a little Red Queen/over-the-top to me so I hope you'll humor a little Alice in Wonderland themed commentary...
Why is a Raven Like a Writing Desk?
Michael Smith (@sideshowbarker to some) replied with some thoughts on it on the W3C Blog with a post entiteled "Getting agreements is hard (some thoughts on Matthew Butterick’s “The Bomb in the Garden” talk at TYPO San Francisco)" in which he points out in short, bullet-list form, several problems with Butterick's statements about how W3C is misportrayed. The post is short enough and already bulleted so I won't summarize here, instead I encourage you to go have a read yourself. He closes up with the point that "Nowhere in Matthew Butterick’s talk is there a real proposal for how we could get agreements any quicker or easier or less painfully than we do now by following the current standards-development process." (emphasis mine).
Indeed, the open source projects mentioned by Butterick are about as much like standards as a raven is like a writing desk and, in my opinion, to replace a standards body with a vague "bunch of open source projects" would send us down a nasty rabbit hole (or through the looking glass) into a confusing and disorienting world: Curiouser and curiouser.
“Would you tell me, please, which way I ought to go from here?"
"That depends a good deal on where you want to get to."
"I don't much care where –"
"Then it doesn't matter which way you go.”
Still, I don't think Butterick really means it quite so literally. After all, he holds up PDF as an ISO standard that "just works" and ISO is anything but an open source project 'like Wordpress'. In fact, PDF and ISO could have some of the same challenges laid against them. For example, from the ISO website:
Are ISO standards mandatory?ISO standards are voluntary. ISO is a non-governmental organization and it has no power to enforce the implementation of the standards it develops.
It seems to me that ISO and W3C have a whole lot more in common than they differ IMO: Standards are proposed by stakeholders, they go before technical committees, they have mailing lists and working groups, they have to reach consensus, etc. Most of this is stated in Michael's post. Additionally though, all PDF readers are not alike either: Different readers have different level of support for reflow and there is a separate thing called "PDF/A" which extends the standard (they aren't the only ones) and adds DRM (make it expensive?). Some readers/authors can accept links to places outside the file, some can't. Some can contain comments added by reviewers or markings, others can't. Etc.
You used to be much more..."muchier."
I think that instead, Butterick is simply (over) expressing his frustration and loss of hope in the W3C: "They've lost their "muchness". You know what? It really does suck that we have experienced all of this pain, and to be honest, Butterick's technical examples aren't even scratching the surface. After 20 years, you really really think we'd be a little further along.
“I can't go back to yesterday because I was a different person then.”
A lot of the pain we've experienced has taken place due to really big detour in the history of Internet standards: The ones we really use and care about were basically sort of put on hold and efforts mostly put toward a "something else". Precisely which something else would have made the Web super awesome is a little fuzzy, but whatever it was you could bet that it would have contained at least one of the letters "x" "m" or "l" and have contained lots of "<" and ">"'s. The browser maker with the largest market share disbanded their team and another major one split up. It got so contentious at one point that the WHATWG was established to carry on the specs that the W3C were abandoning.
While we can't go back and fix that now, the question is: Can we prevent the problems from happening again and work together to make the Web a better place? I think we can.
“Why, sometimes I've believed as many as six impossible things before breakfast.”
The W3C is an established standards body with a great infrastructure and all of the members you'd really need to make something happen. Mozilla CTO Brendan Eich had some good advice in 2004:
What matters to web content authors is user agent market share. The way to crack that nut is not to encourage a few government and big company “easy marks” to go off on a new de-jure standards bender. That will only add to the mix of formats hiding behind firewalls and threatening to leak onto the Internet.
More has happened to drive Web standards and browser development/interoperability forward in the past 2-3 years than happened in the 6-7 years combined and more is queued up than I can even wrap my head around. We have lots of new powers in HTML and lots of new APIs in the DOM and CSS. We have efforts like Test the Web Forward uncovering problems with interoperability and nearly all browsers becoming evergreen - pushing out improvements and fixes all the time. We also managed to get some great reformers elected to the W3C Technical Architecture Group recently who are presenting some great ideas and partnership and cooperation between W3C and other standards bodies like ECMA/TC-39 (also making excellent progress) are beginning. I believe that we can all win with community participation and evolution through ideas like
prollyfill.org (edit: unfortunately we lost that domain to a speculator, but The Extensble Web Manifesto came out of this, and chapters.io and wicg.io now play the respective roles it was advocating) which is trying to team up the community with standards groups and implementers to create a more nimble and natural process based on evolutionary and open ideas... Perhaps that might sound like a marriage of open source ideas and standards that Matthew Butterick would be more happy with... Maybe I should send him an email.
So what do you think?
“Do you think I've gone round the bend?"
"I'm afraid so. You're mad, bonkers, completely off your head. But I'll tell you a secret. All the best people are.”