: '14 Android One; 2 cores (lawlz slow), 512MB RAM, w/ a GPU-ish-sorta-kinda. And we regularly see slower in-market.
-
-
Replying to @slightlylate
: when I said in my talk that what I'm saying on Twitter is the PG version of my conversations with teams here, believe it.
1 reply 0 retweets 3 likes -
Replying to @slightlylate
I'm more of a targets and goals guy. Perhaps the doom and gloom angle is too much for people. Haha
1 reply 0 retweets 2 likes -
Replying to @BenLesh
: this is why I'm focusing on the Time-to-Interactive metric (article soon!) and representative hardware.
1 reply 0 retweets 1 like -
Replying to @slightlylate
: but as with all messages, people need to be ready to hear it.
1 reply 0 retweets 1 like -
Replying to @slightlylate
: over the past year it has become very clear that the SV consensus around frontend tools defends the indefensible.
1 reply 0 retweets 0 likes -
Replying to @slightlylate
: it's not intentional, of course. But real none the less.
1 reply 0 retweets 0 likes -
Replying to @slightlylate
the productivity gains of these modern tools are undeniable, though. And they're all a work in progress.
1 reply 0 retweets 1 like -
Replying to @BenLesh @slightlylate
I'm excited about upcoming build-time tooling around frameworks that reduce the deployed payloads and do code splitting, etc.
1 reply 0 retweets 2 likes -
Replying to @BenLesh @slightlylate
build-time tooling around important weak device and poor network metrics, even estimates, would be great.
1 reply 0 retweets 1 like
: yep yep. This is why Lighthouse matters and why we're investing so much in it.
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.