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 -
Replying to @wycats
that's a surprise. how so?
@samccone@tbreisacher@tdreyno1 reply 0 retweets 0 likes -
the key is that when people don't really understand where the cost is coming from, they take 1/
1 reply 0 retweets 2 likes -
aggressive actions and perform aggressive hacks that can actually make things worse 2/
1 reply 0 retweets 2 likes -
accidentally making lazy code eager, dynamically generating code that deopts, etc. 3/
1 reply 0 retweets 0 likes -
you might be thinking, well sure, but those people made stupid mistakes; in my experience 4/
1 reply 0 retweets 0 likes -
these are smart people making "smart mistakes" that nobody could be blamed for. the only way out 5/
1 reply 0 retweets 0 likes
is to understand where the costs are coming from & how work is parallelized, and then work to 6/
-
-
pare down those costs without inadvertantly introducing others. 7/7
0 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.