One way to think about the declarative vs. imperative debate that arises here (and in nearly every other web API) is a tension between "who do you trust?" (at a baseline level) and "who do you appeal to when that goes wrong?" Base-case trust usually predicts systemic outcomes.https://twitter.com/slightlylate/status/1134337290979794945 …
-
-
Replying to @slightlylate
to be fair, the way this is being rolled out (and the way web audio was butchered) creates the appearance of 'who do you appeal to' being 'no one, unless you pay google money for enterprise support, and the chrome team still ignores you for their own agenda'
1 reply 0 retweets 1 like -
Replying to @antumbral @slightlylate
the answer of 'maybe/probably' to 'will ublock work' is great as a starting point but killing ublock before the answer is 'yes, once it's updated' is also a great way to convince people not to trust you. and the chrome team has done that multiple times (flash, unity, etc)
1 reply 0 retweets 1 like -
Replying to @antumbral
NPAPI deprecation was painful, but we gladly took arrows in the back to protect users. We left that on life support for *years* after Apple killed it, trying to balance equities. As for ublock, they haven't tried to port AFAICT. Looking forward to feedback/data from the effort.
2 replies 0 retweets 1 like
Hitchen's razor is a tough (but fair) master.
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.