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 …
-
Show this thread
-
The alternatives -- waiting to write any code until a standards group pronounces something done, or only ever writing code once someone else ships a feature -- are strictly worse. They'd prevent the platform from moving forward and deprive us of real-world developer feedback.
4 replies 1 retweet 26 likesShow this thread -
Replying to @slightlylate
The problem with this methodology is that by forcing something through, you're running a bet that everyone will buy in. Which, honestly, is a valid approach strategy. But you can't be upset when not everyone else adopts those ideas because they didn't have input.
1 reply 0 retweets 0 likes
Alex Russell Retweeted Alex Russell
I think this misunderstands both our approach, it's built-in openness, and explicit goal to gather timely feedback early. I wrote about it in the posts linked here:https://mobile.twitter.com/slightlylate/status/1181931256537157633 …
Alex Russell added,
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.