The reality is that if our responsibility is to end users then we need to change our approach when the constraints change.
-
-
Replying to @slightlylate
Now, what I didn't do yesterday is to pull up traces from sites or frameworks that haven't made the change.
1 reply 0 retweets 2 likes -
Replying to @slightlylate
That simply wouldn't have been fair or productive. But if you're working on a site/framework, I implore you to get slow devices for a reason
1 reply 0 retweets 7 likes -
Replying to @slightlylate
So yes, Preact + webpack2 w/ route-based code splitting & Polymer App Toolbox are on my tiny "fast enough" list. But want that list to grow!
1 reply 7 retweets 24 likes -
Replying to @slightlylate
If you show me traces that convince me that your tools is fast-by-default, I'll should to the heavens about it too!
1 reply 0 retweets 1 like -
Replying to @slightlylate
Until then, talks like
@addyosmani's later today and@samccone's are essential. The choices our tools are making for us need to change.1 reply 0 retweets 2 likes -
Replying to @slightlylate
I really, really want to go back to talking about PWAs and Service Workers and streams and all the great new stuff my team has been building
1 reply 0 retweets 3 likes -
Replying to @slightlylate
And I promise I will when I see teams succeeding by default more often than not. But that's not reality today. We're not succeeding.
1 reply 0 retweets 2 likes -
Replying to @slightlylate
So if there's urgency in my message it's because of the magnitude of the change we need to make.
3 replies 1 retweet 3 likes -
Replying to @slightlylate
sometimes I'm unclear whether your tweets are talking about politics or web standards.
1 reply 0 retweets 2 likes
: ...it's as though web standards is mostly politics...
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.