Jump to main navigation, main content

Archived entry | Matt Wilcox .net

HTML5 to be released in 2022. W3C are officially a joke.

The news that HTML5 is targeted to be released in 2022 came as the final nail in the coffin of the W3C and the current “Web Standards” movement for me. The W3C is dead, long live the W3C.

The fantastically hard to believe post by Ian “Hixie” Hickson, the lead editor of the HTML5 working group, says everything a developer needs to know about the state of the W3C today. The W3C has become a cancer to the cause of Web Standards, and it needs to be cut out of the equation. It is that simple.

Who the hell knows what the web will be like in 2022? Who even knows what technology the web will be primarily accessed through in 2022 - laptop, mobile, desktop, some new device we haven’t even got yet? The chances of a specification being relevant in another 14yrs are hideously low.

And Ian said of people’s protests at HTML5’s newly re-defined alt attribute: This caused a firestorm of protest from so-called accessibility experts. So-called? These are the people on the WG you are talking about, get your act together, you sound like an idiot! Unfortunately this ass-backward, no-recent-real-world-experience, holier-than-thou attitude seems endemic at the W3C , as far as I’ve seen.


skip to comment form
  1. Andrew Ingram posted 1hrs, 46min, 5sec after the entry and said:

    The changes in HTML5 don't justify it taking this long. Where's all the new form input types that are sorely needed? Being able to define multi-widget inputs to allow better ways of inputting dates without relying on javascript is a must.

    I fully anticipate a point at which people begin just ignoring W3C and begin coming up with their own standards, and I welcome it.

  2. Matt Wilcox posted 14hrs, 9min, 39sec after the entry and said:

    To be entirely honest Andrew, I think we are already at that point. The Webkit team for example are doing far more interesting things with CSS, orders of magnitude faster. People will use the new shiny because it's useful and cool, and then other browsers will have to play catch up.

    The W3C doesn't need to be involved at any point in those proceedings. And I intend to follow Jeff Croft’s example and just use whatever 'things' the majority of browsers support. And screw the W3C, they have become irrelevant to driving progress.

  3. davecc posted 1 years, 80 days, 2hrs after the entry and said:

    At the moment, I can accomplish everything I need with HTML 4.01, but as Andrew said, the changes clearly don't justify it taking sooo long, at the beginning I thought 2022 was a joke heh

From the archives

Other enteries filed under:

My Two Cents

Web Development

Site information

Built with valid XHTML and CSS, designed with web standards and accessibility in mind. Best viewed in a modern browser [Firefox, Safari, Opera]

This domain and all content is a copy of my old website, for historical purposes only.