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
-
-
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 @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 @plinss and
We do exactly that: https://web-confluence.appspot.com/#!/confluence (See "lone omissions")
2 replies 0 retweets 0 likes -
-
Replying to @slightlylate @plinss and
This site is better. Unfortunately Mozilla devs can tell you about many cases where they discovered that WPT tests matched what Chrome shipped but not the spec.
2 replies 0 retweets 2 likes -
Replying to @rocallahan @slightlylate and
WPT is great and I love that work, but it's no excuse for letting Hotlist-Interop bugs languish for years.
1 reply 0 retweets 0 likes
Hear you loud and clear.
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.