claiming that JS parse costs are non-trivial is surprising. can u give a better justification? @samccone @tbreisacher @tdreyno
-
-
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 -
part of what bothers me is that I've been part of a team for the last 18 months whose entire job 1/
-
was to reduce end-to-end time of time-to-interactivity. chasing "bytes-over-wire" was probably 2/
-
the #1 source of wasted time and outright regressions. focusing on eagerly evaluated code 3/
- 3 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.