We often lead, balancing risk/reward rather than demanding a particular point in an arbitrary process. https://www.chromium.org/blink/launching-features … Leadership is rather the point of having an engine team, after all.
-
-
Given that chrome has a near monopoly don't you think you should maybe not ship something as stable before other browsers have it to not reinforce the monopoly?
2 replies 0 retweets 13 likes -
These situations arise only after we: - design in public - beg for feedback (which we usually don't get in a timely way) - write the specs *and* the tests - send designs for wide review - (usually) experiment (via OT) for multiple releases
2 replies 0 retweets 4 likes -
Was Safari’s feedback that the race condition around adding stylesheets was a “show stopper” before, or after this was shipped to Chrome Stable?
1 reply 0 retweets 0 likes -
Replying to @AdamRackis @slightlylate and
Just came here to say: if you're going to beat up on companies and individuals at companies for trying to make things better, we'll end up with a stagnant ecosystem.
2 replies 0 retweets 6 likes -
Replying to @davidbrunelle @slightlylate and
Questioning the decisions that were made by the Google Chrome team, as it affects web standards is “beating up on people?!”
1 reply 0 retweets 1 like -
Replying to @AdamRackis @slightlylate and
Alex has offered a pretty thurough explanation of their process and offered to schedule a call with Rich to discuss. What would "good enough" look like?
1 reply 0 retweets 0 likes -
Replying to @davidbrunelle @slightlylate and
Achieving consensus with other browsers before shipping things (as stable) to the most dominant browser in the world. Why more people aren’t pissed that Chrome is abusing their market power to push their pet projects into the web platform is beyond me.
1 reply 0 retweets 3 likes -
Replying to @AdamRackis @slightlylate and
Have you ever tried to drive consensus amongst a group of people? Try doing the same thing with a group of for-profit companies with competing goals. Waiting for complete "consensus" is how momentum stops.
3 replies 0 retweets 3 likes -
Replying to @davidbrunelle @AdamRackis and
The Chrome team has been the driving force behind many of the capabilities that allow me to build better web apps. If we waited for Safari to lead the way (or catch up), what would that look like?
2 replies 0 retweets 0 likes
The way to really judge this is to look for leadership w/ responsibility. Thankfully we track this: https://web-confluence.appspot.com/#!/confluence (Look at the "lone omissions" tab)
-
-
Replying to @slightlylate @davidbrunelle and
Look at "browser specific" tab for a translation. "Leadership with responsibility" === "we ship as many APIs as we want with utter disregard for anybody else. You don't have the time or resources to implement all the things we push (no matter how badly designed)? Too bad".
0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.