Re:Next-Gen Web Apps: Google unleashes Native Client into Ch...
by extension on Friday August 12, 2011 @11:20AM
(#2877613)
The WHATWG strikes me as exactly what a standards org is supposed to be: enough vendors to form an industry consensus get together and agree to cooperate on certain things for their collective benefit. Or is that the point you were making?
Re:Next-Gen Web Apps: Google unleashes Native Client into Ch...
by leoc on Thursday August 25, 2011 @11:55AM
(#2925290)
WHATWG is certainly efficient at advancing the collective interests of the browser vendors. The problem arises when those interests conflict with the interests of the rest of humanity.
In fairness, the argument you actually made is 'the browser vendors ought to support something only if WHATWG or W3C approves it', which expands to 'the browser vendors should support something only if the browser vendors collectively want to support it, or if W3C approves it'. But that leads to obvious questions. Why is W3C approval critical for technologies of which the browser vendors collectively disapprove, but of distinctly secondary importance for the technologies they collectively like? And when was the last time the browser vendors shown much sign of meekly accepting W3C-approved technologies of which they disapprove? It seems very much as if the WHATWG HTML coup was not only about adopting features which the browser vendors wanted but which W3C was slow to standardise, but also about stymieing features which the W3C approved of but which the brower vendors don't like (like RDFa, namespaces, and HTML modularisation). So setting the W3C up as an alternative gatekeeper here seems almost as cheeky as advancing the WHATWG.