Our take on it is: How do we make adding more overall JS not slowdown start up? Scalability. Takes you down a different route.
-
-
-
: two related things: running less code is always better. Let the browser do what it can. Second, timing matters
- 10 more replies
New conversation -
-
-
delay load?
-
: lots of sites have, e.g., social widgets that only get activated once a user does something. Delay loading these is *huge*.
- 2 more replies
New conversation -
-
-
that’s the Steve rules of being fast! 1. Do less. 2. Be lazy. So good.
-
: wise one, that "Steve" (if that is in fact his real name)
End of conversation
New conversation -
-
-
@nasko Did you see https://www.npmjs.com/package/benice ? onIdle! -
: so sort of an NPM version of this? https://developers.google.com/web/updates/2015/08/using-requestidlecallback?hl=en …
End of conversation
New conversation -
-
-
I feel like JS size is correlated to team size. In my experience, the larger the team the more JS.
-
: ...which says to me that nobody was handed a budget and there's no health indicator for the experience that they can redline = (
- 1 more reply
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.