It seems like I need to be more explicit part 3 in -- specifically for webdevs -- in my blog post series about standards (a small thread): 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/ …
-
Show this thread
-
In addition to being entirely unfit for feature development and iteration (that's what incubation proecesses are for), chartered WG stages have near zero predictive value. I tried to outline why in the previous posts, but it seems worth underlining *that* it's true.
1 reply 0 retweets 0 likesShow this thread -
The takeaway for you, as a web developer is this: dissent of one engine (or even multiple) to a proposal requires an *exrtordinary* amount of background info to unpack, let alone judge well. If you are only watching the performative aspects of the pagent, you'll be disempowered.
3 replies 0 retweets 2 likesShow this thread -
Understanding the forces on the players is time consuming, but wishes for even coastlines don't keep ships from running aground.
1 reply 0 retweets 1 likeShow this thread -
So how to judge a situation? Watch who's willing to lead by shipping (preferably through flags and trials) and prioritises evidence + feedback in decision making.
4 replies 0 retweets 2 likesShow this thread -
Replying to @slightlylate
I don’t think KPIs for browser vendors should include # of new APIs shipped, which seems to be how the chrome team operates. Shipping a bunch of half baked APIs that no other vendor will ever ship is irresponsible and not good for the web.
1 reply 1 retweet 13 likes
This is deep in Not Even Wrong territory. Happy to discuss in a less agro forum. My DMs are open.
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.