: when the things that make development easy make the UX suck, it's reasonable to call them misguided.
-
-
Replying to @slightlylate
: when we were misguided in '05, it was excusable. Pretty new stuff. It's a decade+ later. What's our excuse?
1 reply 0 retweets 0 likes -
Replying to @slightlylate
I was going to say lack of docs.. Async imports by default (or detecting how module is used) would be super useful.
1 reply 0 retweets 0 likes -
Replying to @psimyn
: yeah..hmm. We don't structure our code correctly for this, and that's because we assume we schedule the work, not the browser
1 reply 0 retweets 0 likes -
Replying to @slightlylate
: I've seen a few things that give me hope: HTML Imports, HTTP/2 push, Service Worker cache-ahead for granular imports
1 reply 0 retweets 2 likes -
Replying to @slightlylate
: those things actually let the browser interleave the work and schedule it well.
1 reply 0 retweets 1 like -
Replying to @slightlylate
: but to use them effectively, we've gotta get out of the "JS ALL THE THINGS!?!?!!!" mindset.
2 replies 0 retweets 1 like -
-
Replying to @slightlylate
do you have a good way to measure of time to interactive? e.g. "I can click" vs "I can scroll smoothly"
1 reply 0 retweets 1 like -
Replying to @psimyn @slightlylate
if people just try delaying load but not reducing bloat. 2mb of scripts after onload is still an upsetting experience
1 reply 0 retweets 1 like
: exactly. It's why I stress interactivity. If the main thread is locked up and tapping things doesn't work, it doesn't "work"
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.