And when you look at it, everyone on TC39 is trying their best and doing a great job, and we do have progress, but as a procedure wonk I can't help but blame the need for *complete consensus* for the pace of change in the language.
-
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.
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.
-
-
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?
-
Consensus doesn’t mean unanimity, but it has to mean more than “what Google thinks is a good idea”. Google has some great engineers, but they’re not always right, and can’t possibly take everyone else’s needs and views into account in isolation.
- Još 6 drugih odgovora
Novi razgovor -
-
-
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 …
-
I hesitate to ask how much slower engines should go.
- Još 7 drugih odgovora
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.