So what can we do to mitigate the problem? Given that both Preact and Inferno are way faster drop-in replacements, it might
-
-
Replying to @bmeurer
Is true that dropping those in solves the issues that
@slightlylate refers to? You guys probably see more use cases than we do.2 replies 0 retweets 1 like -
From what we've seen it has no significant impact on start up time which I understand is the biggest issue.
3 replies 0 retweets 1 like -
Replying to @sebmarkbage
: startup on slow phones/networks is dominated by code size. React itself might be fine (if marginal); ecosystem isn't.
4 replies 2 retweets 10 likes -
Are you suggesting that React adds a warning to its docs about bloated libs existing in its ecosystem?
1 reply 0 retweets 5 likes -
Replying to @dan_abramov
: that React points out how hard it is to succeed on mobile with React & work necessary /cc
@sebmarkbage@bmeurer3 replies 0 retweets 1 like -
I guess this wouldn't fly. But fixing the defaults sounds fairly reasonable.
1 reply 0 retweets 0 likes -
It's not that simple. Even with async defaults we'd load too much. Need explicit UI boundaries to split.
2 replies 0 retweets 3 likes -
Replying to @sebmarkbage @bmeurer
: this is why I'm so excited by route-based code splitting in modern frameworks
2 replies 0 retweets 3 likes -
Route based boundaries isn't granular enough but it's something. cc
@thejameskyle2 replies 0 retweets 2 likes
: yes. Need to start there and move to actions/views
/cc @bmeurer @dan_abramov @thejameskyle
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.