and I think we're agreeing that bytes-over-wire is much less important than bytes-in-critical-path
that's true about all frameworks. Built-in components, small helpers, platform-specific code
-
-
it's not easy to ship "chrome-only" code to Chrome, so you ship IE code, then don't run it.
-
ime a huge amount of code, even when careful, is shipped and not immediately used.
- 1 more reply
New conversation -
-
-
u didn't answer my question. i claimed frameworks are on the critical path for sites that use them.
@samccone@tbreisacher@tdreyno -
"framework" isn't one thing -- a framework has code on the critical path and code off it.
-
sure. i'm talking about the "core" part of the framework. the bit that ships on the critical path.
@samccone@tbreisacher@tdreyno -
right but nobody is measuring that; they're measuring react.js.min.gz.
-
i'm not. i'm measuring the website i'm responsible for.
@samccone -
so, here's the deal. i do perf as part of my day-to-day job. so, when i hear
@samccone say "parse time matters" i nod my head 1/ -
because i've seen that shit, yo. i've seen parse times of compiled handlebars templates lock up mobile devices. 2/
@samccone -
Yehuda is saying valid stuff. Parse time in "Parsed" code is critical. Shipping inert code and deferring work is v good
- 1 more reply
New conversation -
-
-
If you could choose one language to be as pervasive as js, what would you pick?
- 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.