2 ms·
In retrospect the practical shifting of web-standards-setting from an at least possibly neutral standards body representing multiple interests (W3C) to a a body
by jrochkind1 8y ago
In retrospect the practical shifting of web-standards-setting from an at least possibly neutral standards body representing multiple interests (W3C) to a a body wholly controlled by browser-vendors (WHATWG)... may have been good for speed of "innovation" for a time, but was in the long-term not good for the "Web as an open platform."
> Making matters worse, the blame often lands on other vendors for “holding back the Web”. The Web is Google’s turf as it stands now; you either do as they do, or you are called out for being a laggard.
Indeed, I think it's the structural politics of WHATWG that make that hard to counter. WHATWG was almost founded on the principles of "not being a laggard" and "doing what we [browser vendors] do". When there were several browser-vendors with roughly equal market power they could counter-balance each other, and had an interest in compatibility with each other, but when there's an elephant in the room...
That is, the W3C folks that were accused of "holding back the web" while trying to keep standards-setting from going to WHATWG... were probably right.
You can disagree, but 10-15 years on, I think we're overdue a larger discussion and retrospective evaluation of the consequences of the WHATWG "coup". I haven't seen much discussion of this, many developers today may not even be aware of the history.