When you see someone upset about "Google only features!!!!!!", consult the Blink Launch Process. We're (sadly) far out ahead and tend to implement first because we aren't starving our platform team. Result is we write code early & iterate. So implement !== ship.https://twitter.com/slightlylate/status/1181702221177577472 …
Your question confuses feature development with standardisation. I tried to outline the relationship in these posts: https://infrequently.org/2018/06/effective-standards-work-part-1-the-lay-of-the-land/ … https://infrequently.org/2018/06/effective-standards-work-part-2-threading-the-needle/ …
-
-
I disagree here. Feature development and eventually adoption drives standardization. They’re not mutually exclusive. This is what Microsoft got wrong about shipping features exclusive to IE at its height.
-
The issue is when a browser that holds a majority of the market ships a feature it pressures other browsers to do the same and compete on a feature without a standard specification. This forces competing browsers and developers to ship something that’s not standardized.
- 1 more reply
New conversation -
-
-
Reading now, thanks!
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.