There's often a plausibility story, but it's very rarely for a good reason. Certainly nothing other apps would use for justification.
-
-
Replying to @wycats @AdamRackis and
There is "return to previous AdWords" option. As I see it, teams should have the right to release features to different browsers gradually
3 replies 0 retweets 3 likes -
The differences between modern browsers are so thin nowadays that there is no justification to not do cross-browser from the start
2 replies 0 retweets 0 likes -
Replying to @DavidBruant @vivainio and
I'm fine for instance that on google docs offline mode is chrome-only. Arguably hard to do well cross-browser. But a no-other-browser wall?
2 replies 0 retweets 0 likes -
Replying to @DavidBruant @vivainio and
I'm fine if it's Service Worker only (standards track stuff with broad consensus but lagging impl is fine)
1 reply 0 retweets 2 likes -
Replying to @wycats @DavidBruant and
When chrome adds new features, then relies on them in apps before there's even consensus to ship, usually something's really wrong.
1 reply 0 retweets 3 likes -
Replying to @wycats @DavidBruant and
Honestly at this point I trust the Chrome team more than the standards bodies that govern these features. Sad, but true.
1 reply 0 retweets 1 like -
Replying to @AdamRackis @DavidBruant and
I do not. Not even a little. 1. Chrome team > TC39?
2. Chrome dominates WHATWG so doesn't make sense to differentiate.2 replies 0 retweets 3 likes -
-
Replying to @matthewcp @wycats and
It's fair to say we invest more in the web and in standards than anyone else. A choice others could easily match!
2 replies 1 retweet 4 likes
I didn't mean my statement in an uncharitable way. It just doesn't make sense to say Chrome > WHATWG because of how much overlap there is.
-
-
Replying to @wycats @slightlylate and
And yes, I sure with Safari was more involved in standards. Excited that they're hosting a TC39 next year.
0 replies 0 retweets 2 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.
