...and because view framework choice sets up so many other choices, it's imperative that these view frameworks message reasonable limits and goals to their users. React's...challenges...there are at least twofold.
-
-
Assuming 2 connections (which, again, is super optimistic), H/2, and not much else hitting the network as we load the site, we can transfer 600KiB, but if we have to wait on JS processing for the majority of the payload, we're down nearer to 200KiB.
-
So if you take "modern" frontend, leave no room whatsoever for 3rd parties, and need to reach all users, a 40K framework is a 20% tax. If you have to reach the P90 user *today*, you can afford even less.
End of conversation
New conversation -
-
-
It is frustrating that the US infra is behind most of the industrial world on internet.. and exactly why size opt for *beyond framework* matters, but not the stdlib. So afaict, it comes down to CPU time for a semi-decent ARM chip to lazy load 50KB... how much is it? 200ms?
-
Cheap devices don't have "semi decent" ARM chips, they have the dregs of 2014's race to 64bit on a shitty 28nm process. They can't frequency scale, they have no cache, and their main-memory latency is *horrific*.
- 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.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.