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
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.
-
-
...and it isn't possible to solicit feedback privately or to a privileged group of insiders without opening oneself to charges of favoritism. So we use public mechanisms, like that blog post. So what about it would you like to see changed?
-
Just slowing down the number of features being pumped out would be huge. If Google's goal is a vibrant web, maybe some of that Google talent could be redirected from new web features to catching other browsers up.
- 4 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.