this is nuanced, but the generality of the cost of parse time stands on its own.
-
-
and I think we're agreeing that bytes-over-wire is much less important than bytes-in-critical-path
-
you may, for example, want to include some extra bytes so subsequent interactions don't trigger 1/
-
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
-
in my experience, this is a second optimization. cutting critical path bytes makes a bigger diff.
@samccone@tbreisacher@tdreyno -
I have seen even critical-path bytes (which nobody really measures) really mislead people.
-
more directly, if critical-path-bytes was the metric, why is everyone measuring the size of libs?
-
because they're often on the critical path?
@samccone@tbreisacher@tdreyno - 6 more replies
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.