3 ms·

It's not true, to w3c's surprising credit. What Google does, is publish a "draft" which is as far from a standard as their authors are from the Moon. This give

It's not true, to w3c's surprising credit. What Google does, is publish a "draft" which is as far from a standard as their authors are from the Moon. This gives Chrome the leeway to call it an "emerging standard" and just ship it. It doesn't care if there are objections, or that other browser vendors will not implement it. It's now a "standard" in Google's dictionary. For something to become a W3C standard even in the present world, you need a consensus and at least two independent implementations. None of that exists for stuff Google pushes out (hardware APIs, web transport, constructible stylesheets [1], the list goes on...). The correct name for those is Chrome-only non-standards. [1] These one isn't even a draft. It is.... "a collection of interesting ideas" in a working group https://wicg.github.io/construct-stylesheets/ https://wicg.github.io/construct-stylesheets/ Shipped by default in Chrome, of course

jacooper 4y ago
Chromium only, not chrome only
- dmitriid 4y ago
  Those non-standards are aggressively pushed by Chrome, and shipped by default by Chrome first. Calling it Chromium makes it sound like they somehow originate in the "open-source" version. They don't. We have to call them what they are.
  - jacooper 4y ago
    TIL, I though chromium always was ahead of chrome, so all changes end up in chromium first, therefore also other chromium based browsers get the patch/nonstandard behavior.
    - dmitriid 4y ago
      Chromium might get those features purely due to Chrome's release cadence. So the code may be enabled the code base without flags before it ships in Chrome (Chrome releases are monthly). Most of Chromium-based browsers will probably lag on those features because they either don't want them, or have their own release cadence, or are running an older version etc. And it's only Chrome that pretends that their non-standard features are standard, and employs a large network of propaganda from web.dev[1] to dev rels[2] to advertise them as standards. [1] Example WebTransport https://web.dev/webtransport/ https://web.dev/webtransport/, multiple non-standard hardware APIs https://web.dev/devices-introduction/ https://web.dev/devices-introduction/ [2] I sadly lost the link to tweet from either Justing Fagnani or Alex Russel where they called the decision to ship Constructible Stylesheets "bravery to move the platform forward". Context: trivial deadlock issues in the spec, both Mozilla and Safari were dead set against it until issues could be fixed, Google-led lit-html wanted the functionality, so Chrome just shipped it.

jacooper 4y ago

Chromium only, not chrome only

dmitriid 4y ago
Those non-standards are aggressively pushed by Chrome, and shipped by default by Chrome first. Calling it Chromium makes it sound like they somehow originate in the "open-source" version. They don't. We have to call them what they are.
- jacooper 4y ago
  TIL, I though chromium always was ahead of chrome, so all changes end up in chromium first, therefore also other chromium based browsers get the patch/nonstandard behavior.
  - dmitriid 4y ago
    Chromium might get those features purely due to Chrome's release cadence. So the code may be enabled the code base without flags before it ships in Chrome (Chrome releases are monthly). Most of Chromium-based browsers will probably lag on those features because they either don't want them, or have their own release cadence, or are running an older version etc. And it's only Chrome that pretends that their non-standard features are standard, and employs a large network of propaganda from web.dev[1] to dev rels[2] to advertise them as standards. [1] Example WebTransport https://web.dev/webtransport/ https://web.dev/webtransport/, multiple non-standard hardware APIs https://web.dev/devices-introduction/ https://web.dev/devices-introduction/ [2] I sadly lost the link to tweet from either Justing Fagnani or Alex Russel where they called the decision to ship Constructible Stylesheets "bravery to move the platform forward". Context: trivial deadlock issues in the spec, both Mozilla and Safari were dead set against it until issues could be fixed, Google-led lit-html wanted the functionality, so Chrome just shipped it.