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.
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?
-
-
(in case it isn't clear, this is an honest question; we engage in public for more of the process because Google funds our team at a level that's more in line with what a vibrant web needs, while other vendors don't, and being out of line is uncomfortable for us too)
-
The net result would likely be more features, shipped faster, but with less rounding-off-of-the-dangerous-parts. That is, we pay a high "get it right" tax, and part of that is the level of early transparency required for standards-track stuff in order to solicit feedback.
- 6 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.