An abridged list of requirements to use React the way FB does for mobile web: - staff dedicated performance team - set hard perf targets that no CL can violate (enforced by CI) - have a separate "mbasic" version of the service and send users to it that can't handle heavy JShttps://twitter.com/mikeal/status/1159165205428879360 …
If it FB were talking about the discipline they have to employ to make React work (the way I'm describing the FB/Google prior restraints on slowness), would that help?
-
-
I’m curious if that is the case in general though at that scale. I’m sure there are trade offs they would be making and have to employ people for other solutions also.
-
At the scale we're talking about, performance correlates *super directly* to money and engagement (hence management is happy to put big roadblocks in the way of doing slow stuff).
- 1 more reply
New conversation -
-
-
There's a huge gap in the community understanding of what it takes to get and stay fast. The amount of tooling and discipline -- particularly when you start with a high tax rate -- is intense. This isn't helping: https://reactjs.org/docs/optimizing-performance.html …https://reactjs.org/docs/code-splitting.html …
- 1 more reply
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.