: two related things: running less code is always better. Let the browser do what it can. Second, timing matters
-
-
Replying to @slightlylate
: I see lots of React apps screw themselves by loading everything up front; webpack and script-centricness defeat browser help
1 reply 0 retweets 1 like -
Replying to @slightlylate
: if you could break up the work and load modularly, when needed, that can work... but that's not where React apps are at today
2 replies 1 retweet 1 like -
Replying to @slightlylate
: I traced an app yesterday that had 7s of eval + mountComponent() work (on an android one device)
2 replies 0 retweets 2 likes -
Replying to @slightlylate
: developer was doing the natural thing; re-inventing the platform instead of working with it put them in an unwinnable position
1 reply 0 retweets 1 like -
Replying to @slightlylate
: I see this pervasively across big frameworks; React only the furthest down the rabbit hole today.
1 reply 0 retweets 2 likes -
Replying to @slightlylate
: letting browsers schedule work and loading modules granularly is the holy grail. We need architectures that enable this.
1 reply 0 retweets 3 likes -
Replying to @slightlylate
: "time to interactive" matters a lot more than our tools and architectures acknowledge.
1 reply 1 retweet 4 likes -
Replying to @slightlylate
It is one of our top metrics. It is a problem. Something needs to be fixed but the route to fix it is different.
1 reply 0 retweets 3 likes -
Replying to @sebmarkbage @slightlylate
I'm going to write a post about my findings to clarify my perspective. Twitter makes this really vague.
1 reply 0 retweets 6 likes
: would love to read that.
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.