ok, i think we agree on this. but for js on the critical path, @samccone is right, yeah? @tbreisacher @tdreyno
-
-
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/
-
got us closer, but looking closely at how the browser parallelizes work, restructuring payloads 4/
-
identifying and eliminating slowdowns in the initial evaluation (deopts, etc.) all had a big 5/
-
impact, but competed against efforts that were counterproductive. Just lived experience here 6/6
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.