3 ms·

What standards are lacking?

• dmitriid 7y ago
  Just an example, quoting Dan Abramov [1]: "Features like service workers are touted as a solution to many problems in the web, but their ergonomics are so under-designed that people actually have to change domains to bust the cache from a broken build (I’m not making this up)." Service Workers is drafted by 4 people. 3 of them are from Google. [2] A lot of standardisation work on web standards is completely taken over by Google. A lot of discussions on JS and HTML are being handled by the same group of ten or so people who are in every open issue and every open proposal on GitHub. A common thread is "oh yes, we should involve the wider web community that's why we reached out to Angular and Polymer for comments", which are, unsurprisingly, also Google projects. A recent proposal where I saw this happen is a proposal by Apple, Template Instantiation [3] Which is now almost entirely taken over by Google. See for example this issue: [4]. Three engineers from Google decided on the future of the project and chose only Angular and Polymer as the frameworks to talk to. And you can see this everywhere. [1] https://dev.to/dan_abramov/comment/6kh1 https://dev.to/dan_abramov/comment/6kh1 [2] https://w3c.github.io/ServiceWorker/ https://w3c.github.io/ServiceWorker/ [3] https://github.com/w3c/webcomponents/blob/gh-pages/proposals/Template-Instantiation.md https://github.com/w3c/webcomponents/blob/gh-pages/proposals... [4] https://github.com/w3c/webcomponents/issues/747 https://github.com/w3c/webcomponents/issues/747
• dmitriid 7y ago
  More. Just today: https://twitter.com/Rich_Harris/status/1161642299761266689 https://twitter.com/Rich_Harris/status/1161642299761266689 Quote: “This spec (whose three editors are all Googlers) was shipped in Chromium and presented as a fait accompli despite objections.” More at the link