The path is always: DESIGN → ITERATE → SHIP & STANDARDISE
-
Show this thread
-
I get into some of it at length here: https://infrequently.org/2018/06/effective-standards-work-part-2-threading-the-needle/ …
1 reply 0 retweets 4 likesShow this thread -
The important thing to recall is that the earliest work that led to the core of what our major WGs tend *didn't happen in committee either* So why would we expect new things to be different?
1 reply 0 retweets 1 likeShow this thread -
And yet we do. Insiders are always keen for work to happen in the rooms they're already in (where they have implicit veto and social capital from previous battles won/lost). For early stage exploration, this is a trap!
1 reply 1 retweet 3 likesShow this thread -
The insiders don't feel the glacial rate of progress as a problem...they're too busy as it is! And folks presenting upstart ideas didn't convince all the old-timers that their thing was really *needed*...we've gotten by without it, after all! And we work by consensus here, soo...
1 reply 0 retweets 2 likesShow this thread -
These forums are toxic for exploration and iteration of big new things because *that's not what they're chartered to do*. Never were, never will be (see previous thread).
1 reply 0 retweets 3 likesShow this thread -
In conclusion, WGs that tend to the care and feeding of important systems didn't spring fully formed from the head of Zeus either! It's unreasonable to expect such miracles to happen at *any* moment, past or future, so we use CGs and incubation to make safer spaces for new ideas.
1 reply 0 retweets 1 likeShow this thread -
Replying to @slightlylate
Guessing these threads are precipitated by <toast>… It’s good for folks to understand how various groups work. However, reaction to <toast> is pretty telling & widespread. IMO Google needs to message its exploration better, and folks don’t need to know about this as much.
2 replies 0 retweets 1 like -
Replying to @jfbastien
I've been thinking a lot about how other vendors tend not to implement early, and generally don't have the bandwidth to explore (structurally under-funding their web platform teams), so i2i looks late-stage because for them it *would* be.
1 reply 0 retweets 0 likes -
Replying to @slightlylate
I’m not talking about Apple here. Im saying a bit of introspection seems warranted. Sure Apple can introspect too! But <toast> seems rather self-inflicted, even if well intended and part of a process that nominally seems palatable.
1 reply 0 retweets 1 like
Some large fraction of the push-back seems to have been from folks who want to put WGs into the center of the early design phase for features. Add a dash of mistrust and a smidge of process opacity and voila!
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.