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.
On feedback from other's proposals, Mozilla's positions repo is an interesting way of handling this sort of review flow. We have thought about something similar. Frustrating that Chromium is so far ahead on features that we tend to be the ones pushing most new work = (
-
-
What I'm trying to question is why having the most new features means you're the farthest ahead. When the web platform was new and not very expressive, maybe, but these days shouldn't development processes focus on security, privacy, performance, consistency over features?
-
Larry pretty much summed up Mozilla’s position on the matter (and it sounds a lot like what I hear from Apple folks too). I think we are only working on a tiny handful of new APIs, while investing big on privacy, security, perf, etc.
- 3 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.
A part of the disconnect is that we're more interested in developer feedback and sentiment than formal WG approval. WG's aren't fitness functions.