What process does Google go through to add new web platform features to @googlechrome / @ChromiumDev?
How do they balance moving fast with preserving browser compatibility, and broader collaborations with the web standards ecosystem?
@slightlylate explains:
https://twitter.com/slightlylate/status/1167454620018331653 …
-
-
Replying to @bgalbs @googlechrome and
BTW, calling this the process *Google* goes through for an engine that's now used widely beyond Google makes it sound/look like Google is in charge of Chromium. is that the case?
1 reply 1 retweet 1 like -
-
Replying to @ericlaw @marypcbuk and
At the risk of taking the bait, well-run OSS projects equate investment with a seat at the table over the long-run. This tends to lead to high-quality contributions, which tends to lead to, e.g., representation within the API OWNERS group: https://chromium.googlesource.com/chromium/blink/+/refs/heads/master/OWNERS …
2 replies 0 retweets 1 like -
Replying to @slightlylate @ericlaw and
One of our persistent challenges with representation is that we (Google) keep hiring the best folks when they make it known they're looking
2 replies 0 retweets 1 like
(FWIW, I support Google continuing to offer high-quality positions to high-quality people; I just wish we had more competition)
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.
Hullo! Friendly Standards TL & Blink API OWNER here, can answer questions about our process.