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.
-
-
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 @plinss and
You can improve the Web as a platform, and simultaneously mollify us engine diversity absolutists, by redirecting Chrome resources to move *faster* in the right areas --- namely, fixing interop issues, even just the issues that Google already agrees should be fixed.
2 replies 0 retweets 5 likes -
Replying to @rocallahan @slightlylate and
I'm going to have to mention the WebRTC Unified Plan fiasco again. That was about 4 years between Firefox shipping the spec Google agreed on and Chrome finally shipping it by default, during which time Firefox really suffered for not supporting Google's non-standard API.
1 reply 0 retweets 3 likes -
Replying to @rocallahan @slightlylate and
Here's another good one (not randomly sampled, just one that I was involved with). I filed the bug in 2012, got "Hotlist-Interop" (thanks
@RickByers) in 2015, took 3 more years to actually fix. https://bugs.chromium.org/p/chromium/issues/detail?id=123004 …1 reply 0 retweets 2 likes -
Replying to @rocallahan @slightlylate and
When Chrome devs talk about the importance of velocity, these are the bugs I think about.
1 reply 0 retweets 0 likes -
Replying to @rocallahan @slightlylate and
I admit we have work to do to consistently prioritize feature and bug work for maximum web developer bang-for-the-buck. WIP, related to MDN survey and DSAT metrics.
1 reply 0 retweets 2 likes -
Replying to @RickByers @slightlylate and
I don't trust that formulation. People can argue --- some *are* arguing --- that Web developers are best served by abandoning interop altogether and adopting a Chromium monoculture.
2 replies 0 retweets 1 like
We're not arguing that.
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.