Hixie's criticisms of it were correct, and WHATWG was the kick in the pants that the W3C needed to focus on relevant things again.
Hixie's criticisms of it were correct, and WHATWG was the kick in the pants that the W3C needed to focus on relevant things again.
There are legimate disagreements over whether switching to XML was a good idea. Nonetheless, these disagreements were not a good excuse to overthrow W3C entirely, merely a convenient excuse for the browser vendors. Moreover, I don't think the HTML standards need to move as fast as Google wants them to move. HTML is now a "living standard", in other words, constantly changing, and I don't think that's good for the web. These things should move slowly. The giant browser vendors themselves are selfishly the main beneficiaries of forcing everyone else on the web to move at their pace. It consolidates their monopolization of the web.
> WHATWG was the kick in the pants that the W3C needed to focus on relevant things again.
Relevant things like... not controlling the HTML standard anymore? WHATWG has stolen a lot of the relevance of W3C.
And of course WHATWG didn't out-convince devs on a marketplace of ideas; as an oligopoly of browser developers they just did.
These days, W3C stuff seems perfectly fine (except for their standard document template making it almost impossible to tell “what is this thing actually about?” at a glance! )