Don’t break the web, that is the number one goal. So it is not fair nor accurate to compare Web/JS with other platforms and languages. Few have as much responsibility and reach, and such any change needs to be thoroughly thought through.
-
-
Replying to @Kevin_Kamimura @mikesherov and
Actually my #1 goal is to slow/stop the web's slide into irrelevance. Broken things can be fixed. Irrelevant things are rarely reserected!
4 replies 0 retweets 12 likes -
Replying to @RickByers @mikesherov and
Irrelevance for whom? Maybe not being able to use the web as a tool, to compete with native platforms makes it irrelevant for Google, but Google doesn’t speaks for everyone. Without engine diversity the web is no longer open, and that is its largest appeal over native.
2 replies 2 retweets 6 likes -
Replying to @Kevin_Kamimura @RickByers and
Engine diversity absolutists need to describe what concrete benefits it provides that can't be achieved other ways in the medium-term (e.g., OSS forking, which has created huge divergence in the KHTML-lineage engines)
8 replies 0 retweets 2 likes -
Replying to @slightlylate @Kevin_Kamimura and
This is unworthy of you, Alex.
1 reply 0 retweets 7 likes -
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
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 …
-
-
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 - 5 more replies
New conversation -
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.