network fetches. those bytes will have a net positive impact on the early user experience 2/
-
-
but the "bytes-over-wire" metric will tell you to force another XHR. 3/3
1 reply 0 retweets 2 likes -
Replying to @wycats
in my experience, this is a second optimization. cutting critical path bytes makes a bigger diff.
@samccone@tbreisacher@tdreyno1 reply 0 retweets 0 likes -
I have seen even critical-path bytes (which nobody really measures) really mislead people.
2 replies 0 retweets 0 likes -
more directly, if critical-path-bytes was the metric, why is everyone measuring the size of libs?
1 reply 0 retweets 1 like -
Replying to @wycats
because they're often on the critical path?
@samccone@tbreisacher@tdreyno2 replies 0 retweets 1 like -
false ;)
3 replies 0 retweets 1 like -
Replying to @wycats
so, wait, is it the case that some part of ember is not on the critical path for an ember site?
@samccone@tbreisacher@tdreyno1 reply 0 retweets 0 likes -
that's true about all frameworks. Built-in components, small helpers, platform-specific code
3 replies 0 retweets 0 likes -
it's not easy to ship "chrome-only" code to Chrome, so you ship IE code, then don't run it.
2 replies 0 retweets 1 like
ime a huge amount of code, even when careful, is shipped and not immediately used.
-
-
Replying to @wycats
this is also my experience. specifically, that code is shipped on the critical path.
@samccone@tbreisacher@tdreyno0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.