Hullo! Friendly Standards TL & Blink API OWNER here, can answer questions about our process.
-
-
Replying to @slightlylate @bgalbs and
CSS modules have been led by our friends at MSFT -- in fact, they're part of a package of module-like-things they've been pushing forward. Initial plan was to start with HTML modules as a replacement for Imports...but in standards conversation, went with less risky types first
1 reply 1 retweet 4 likes -
Replying to @slightlylate @bgalbs and
They're being driven through our tortuously open process which places a higher set of hurdles in front of features we're out ahead on.
1 reply 1 retweet 1 like -
Replying to @slightlylate @bgalbs and
Some features are super low risk -- e.g., places where we're playing catch-up with other engines. For those features, there's a form of our process called "Intent to Implement and Ship". If your situation is simple, it's easy-ish.
1 reply 1 retweet 1 like -
Replying to @slightlylate @bgalbs and
If, on the other hand, you're leading on a new feature for the web...hoooooby, does the bar get high. There are separate phases for implementation, experimentation, and shipping, and the OWNERS (myself included) interrogate the teams, looking to make sure they've got a good case
1 reply 1 retweet 2 likes -
Replying to @slightlylate @bgalbs and
...after all, anything we ship to Stable out from behind a flag is something we're stuck with ~forever. So our process focuses heavily on gathering evidence that lets us judge 2 things: * does this feature solve an important problem? * does it solve it well?
2 replies 1 retweet 4 likes -
Replying to @slightlylate @bgalbs and
All of this makes sense, but I'd like to comment on something Mike said. I often see new Chrome things announced as "web" features which to me implies they are already standard, in multiple browsers, etc. It's not a web feature if it's just Chrome. Maybe that's just me though. ;)
1 reply 0 retweets 1 like -
Replying to @raymondcamden @slightlylate and
This ^. I follow the standards process for many specs, and most of the people on them are clear that APIs and experimental or origin trial. My frustration has been announcements/blogs that state things as web features when they haven’t shipped. That’s the frustrating part
1 reply 0 retweets 1 like -
Replying to @mhartington @raymondcamden and
Let's interrogate that a bit. What frustrates you about a blog post like this?https://developers.google.com/web/updates/2019/08/contact-picker …
3 replies 0 retweets 1 like -
Replying to @slightlylate @mhartington and
There's a legacy way of working that some folks prefer where feature developers lock themselves in a room and ship whatever the folks who *happen* to be in the room understand to be good.
1 reply 0 retweets 0 likes
That way of working puts consensus formation at the very front of any public engagement. It has been our experience that this is a reliable recipe for making expensive mistakes.
-
-
Replying to @slightlylate @mhartington and
So, instead, we do everything we can in the open...and "open" != "in a meeting of a chartered working group" So you get to see the sausage being made *because we need your help to improve it*
1 reply 0 retweets 0 likes -
Replying to @slightlylate @mhartington and
I could reduce our costs in shipping APIs by having us "pull an Apple" -- droppping stuff into the product fait-accomplis, then spending our standards energy arguing against deviations to what's shipped. You'd have less of a voice in that model. Is that better?
1 reply 0 retweets 0 likes - 8 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.