yeah, @slightlylate and I have DMs going. But this isn't about the intricacies of the Blink Launch Process, with all its confusing terminology. The dynamics are more subtle than that. If Google ships something, it automatically puts pressure on other vendors to follow suit, and
Imagine trading places with a browser engineer. A standards body stamps a clearly problematic design with their seal of approval. Neither you nor any of your engine builder peers think it's a good idea. Does it get implemented, particularly when doing so means taking a risk?
-
-
All good design work -- the stuff that gets to eventual interop and which folks don't hate -- is the result of a collaboration between platform developers and web developers. One party calling the shots never works, and putting standards before design iteration doesn't either.
-
I'm sure the browser engineers would hate it, just as companies often hate adhering to regulations and laws dreamt up by governments and lawmakers. The answer in both cases is for the rule-setters to take the advice given by industry seriously, without ceding power to it
- 3 more replies
New conversation -
-
-
Imagine trading places with a web dev. A bunch of people who have never built a complex web application (or a web site more complex than a simple static HTML page) decide the future features of the web platform as a whole. Attached is a quote from Dan Abramov 1/pic.twitter.com/2fhE2D98gt
-
And when there are proposals such as Template Instantiation, and the question of "let's discuss this with framework/library authors, shall we?" comes up, the only frameworks chosen for discussion are suspiciously under Google's umbrella: Polymer and Angular 2/2
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.