Again, it depends what you mean by consensus! Do you mean full absolutely zero detractors every time consensus? Even given unequal investment and motivation from all participants? Or do you mean Rough Consensus, where sometimes a thing has to move from theory to reality to learn?
-
-
So what is an ideal scenario? Imagine multiple engines all compatible about 99% of features all the time, exploring the frontier of new features separately, but safely, then quickly converging. Assuming such a scenario represents a competitive platform, that's pretty

-
To enable that ideal scenario, Blink invests massively in compat, tests, OT infra, process, etc. One concern now is that we've done a huge amount to get compat for existing features but are pulling away on investment levels for new work, endangering competitiveness.
- 6 more replies
New conversation -
-
-
Also, incase it's not 100% clear, Chrome team expects to continue to invest heavily in all that's required for healthy engine diversity: specs, conformance tests, SDOs etc. If anything our investment there just keeps going up.
-
If that were to ever change to reflect some desire for "engine monoculture" it would be very clear, eg. from TPAC attendance numbers. All that travel and time away from work could never be justified by PR alone
. And that's a drop in the bucket compared to the eng costs.
End of conversation
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.