DMdmitriid·Nov 1, 2020
> One could argue whether a feature that has existed for over a decade and is only used by 1-2% of page views is worth improving, but that is not the argument that domenic is making here.
> It's interesting that these refer only to the implementation cost to Google, and does not make any reference to costs or benefits to other users of the web platform, which are discussed by other comments.
A few months back Chrome shipped Constructible Stylesheets. The proposed specification was strictly opposed by other browser vendors, with Safari stating that they will not ever consider implementing them in the current state [1].
Chrome not only shipped it enabled by default, but refused to bring it back under a flag because "is used on about ~.8% of page loads in Chrome now" [1] (safe to assume, all of them are Google users and users of Google-devel
Read the rest
oped libraries).
It's the most recent example (also backed up by numbers provided by Google themselves). I won't even mention the plethora of standards that other browser vendors consider harmful, but are enabled by default in Google.
So yes, Google is only concerned by the cost to Chrome, never by the costs or benefits to other users of the web platform.
> it looks like the process of discussion does not exist at WhatWG anymore, and that Google basically dictates terms.
That is true. The standards process (both w3c/whatwg and tc39) is hijacked by the same 3-4 people from Google, and decisions are rammed through irregardless of anyone.
[1] https://github.com/WICG/construct-stylesheets/issues/45#issu...
[2] https://github.com/WICG/construct-stylesheets/issues/45#issu...