This is unworthy of you, Alex.
-
-
Replying to @torgo @Kevin_Kamimura and
Asking that we understand our values, rather than simply using them as a cudgel? I hope not.
1 reply 0 retweets 1 like -
Replying to @slightlylate @torgo and
FWIW, I can make a strong case for engine diversity (ceteris paribus), but not one that trumps platform competitiveness. The mental exercises to demonstrate where you personally come down on this aren't hard to conjure.
2 replies 0 retweets 1 like -
Replying to @slightlylate @torgo and
In plain language, Web competes with Native. Google has a native platform but with as little lock in as possible (no hardware, payments nor browser lock in). Apple has a native platform with complete hardware, revenue and browser lock-in. Which do you think wants Web to win? 1/2
2 replies 2 retweets 6 likes -
Replying to @mikesherov @slightlylate and
Not nefariously, but Apple has less incentive in the web winning, and underinvests in Safari. Now, imagine Google, trying desperately to get the Web to win, but gets beat up for it because it doesn't always wait for perfect consensus. Again, G err'd with aSS, but not much more.
1 reply 0 retweets 6 likes -
Replying to @mikesherov @slightlylate and
The problem with “wanting the web to win”, but not being willing to wait for consensus about what the web *should be* is that it turn the _open_ web into Google’s web. Which is just another way of destroying the web.
2 replies 13 retweets 33 likes -
Replying to @plinss @mikesherov and
This is a bit over-the-top wrt adoptedStyleSheets. Pulling the thread, they were discussed at TPAC in '16 & '17, iterated on in public w/ collaboration from developers, and only shipped in '19 after spec and tests were in place.https://groups.google.com/a/chromium.org/forum/m/#!topic/blink-dev/gL2EVBzO5og/discussion …
1 reply 0 retweets 3 likes -
Replying to @slightlylate @plinss and
I hesitate to ask how much slower engines should go.
3 replies 0 retweets 0 likes -
Replying to @slightlylate @mikesherov and
There’s always going to be tension between “move fast and break things” and slow and careful deliberation. This is a good thing, it’s fine to put pressure in either direction when there are valid concerns.
1 reply 0 retweets 0 likes -
Replying to @plinss @mikesherov and
Invoking FB's motto (not ours) suggests you might be overfitting some bias.
2 replies 0 retweets 0 likes
If the Blink Launch Process -- ridiculously long and painful as it is -- had a motto, it'd be more like "move deliberately, show your work, and be a good neighbor": https://www.chromium.org/blink/launching-features …
-
-
Replying to @slightlylate @plinss and
Adam Rackis Retweeted Adam Rackis
This thread has been brutal. I’ll hope and assume you didn’t see this, and I’ll further hope the answer is favorable to Chrome https://twitter.com/adamrackis/status/1221490716527951872?s=21 …https://twitter.com/AdamRackis/status/1221490716527951872 …
Adam Rackis added,
Adam Rackis @AdamRackisReplying to @slightlylate @plinss and 6 othersWere the issues that have been shown above raised before, or after you guys shipped this to stable? In particular Apple’s oft-quoted “show stopper?” If they only brought that shit up after it was in stable then I’ll take back just about every bad thing I said about Chrome, here.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.