What do you mean by client overhead in this context?
-
-
-
-
Replying to @threepointone @Rich_Harris and
bundlephobia needs to add parse/execution time. download size is only part of the problem
1 reply 0 retweets 2 likes -
Replying to @rossipedia @threepointone and
There is a lot of hidden cost to bundle size. Debugging, domain knowledge etc
1 reply 0 retweets 2 likes -
Replying to @richardiii @threepointone and
well, yeah... which is still only part of the problem. I wasn't trying to diminish its role, rather point out that parse/execution time are often overlooked and play as big a role in the end-user experience
2 replies 0 retweets 4 likes -
Replying to @rossipedia @richardiii and
Is there an easy way to get parse/execution time?
1 reply 0 retweets 0 likes -
Replying to @matthewcp @richardiii and
it's a bit complicated, as that depends quite a bit on what device it's running on. but a couple baselines numbers measured from popular devices would be helpful (iPhone, Galaxy, and possibly a lower end device as well)
1 reply 0 retweets 0 likes -
Replying to @rossipedia @richardiii and
Sorry, I was asking if you know of a way for a tool like bundlephobia to get this information (rather than rely on people to provide it for their own stuff)?
1 reply 0 retweets 0 likes -
Parse is streaming, so in a bundle this big (yeoooowwwza!!!), it's probably hidden by threaded parsing; main-thread exec component isn't. I'd just run it with wpt/puppeteer on a real device to get the time
-
-
Replying to @slightlylate @Rich_Harris and
The delay will materialize counterintuitively: on a slow link, a whopper like this is a late long task (hope rendering isn't blocked by it!! interactivity *clearly* will be), whereas on a fast link this will contend for both CPU and network time earlier in the timeline.
1 reply 0 retweets 1 like -
Replying to @slightlylate @Rich_Harris and
So this looks to be in the "please don't" pile of deps. Architect out if you can.
0 replies 0 retweets 0 likes
End of conversation
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.