The important point here is that what the web needs is a set of browsers/engines competing *at the leading edge*. Multi-year delays in delivering features to 90+% of users are all-too common, and the problem isn't update rates any more.https://twitter.com/jyasskin/status/1207739254480048128 …
-
-
Chrome team re-engaged on v1 design in '15 under the presumption that Mozilla circa '14 objections were good-faith and that everyone who showed up to re-litigate v0 design would keep faith with users waiting for the new stuff and implement in a timely way.
Show this thread -
We'll have full coverage come the Anaheim launch, but nothing was gained for the delay. Engine diversity is a s good as it's fruits.
Show this thread
End of conversation
New conversation -
-
-
It still doesn’t work in Safari.
-
Sorry? There's one principled divergence (`is` attr). Everything else works. You simply can't equate that with Mozilla's multi-year delay to ship *anything*.
- 9 more replies
New conversation -
-
-
@marcosc I think it's because working devs would like things that are easy to code, are performant without a heap of JavaScript (frameworks or otherwise), and that don't keep getting reinvented every time a new framework/component library comes out. -
I understand the rationale and why, but what’s the point when none of this stuff works across browsers? I still need heaps of JS to get any of it to work. That wouldn’t change with new tags. So then I have new tags and have to pick a polyfill library or framework too. Sigh.
- 3 more replies
New conversation -
-
-
Speaking of knifing, `beforeinstallprompt` is next in line
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.