Sometimes we get things wrong! But as often as not these days, we just can't get feedback from other vendors in a timely way. It's a direct consequence of them starving their platform teams of staff.
-
-
But the big question here is this: why are *browser vendors* in charge of web standards, as opposed to a faction within a larger group of stakeholders (a la TC39, though ideally without the same financial commitments) that can advise on implementation pitfalls?
-
I wrote a blog post series on some of this: https://infrequently.org/2018/06/effective-standards-work-part-1-the-lay-of-the-land/ … https://infrequently.org/2018/06/effective-standards-work-part-2-threading-the-needle/ … TL;DR: feature development and standardisation are separate-but-related processes, and the folks who ship the bits take the risks.
- 15 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.