glad you all do. Just think it's a blanket statement, & there are specific solvable problems. I've heard "React not even close to prod rdy"
-
-
Replying to @jlongster @sebmarkbage
Mostly from the
@slightlylate s of the world. I've heard "ember is disqualified" despite many prod users.1 reply 0 retweets 2 likes -
Replying to @wycats @jlongster and
I think it's just too easy to build un performant react native apps
1 reply 0 retweets 1 like -
Replying to @C4C_Recruiting @wycats and
also i think react isn't supposed to be fast, but instead usable through large enterprisey teams. built for collab not speed.
2 replies 0 retweets 1 like -
Replying to @C4C_Recruiting @wycats and
The sticky issue is the distribution model; RN (& Cordova, etc.) spots you first-run via heavyweight install step.
3 replies 0 retweets 3 likes -
Replying to @slightlylate @wycats and
The web's superpower is ephemeral use. If first run is unusably slow, who's gonna stick around for another go?
2 replies 2 retweets 13 likes -
For content, SSR is a good "first run" trick. Fast first run + competitive second run is a hard engineering problem.
2 replies 1 retweet 0 likes -
SSR is fine if TTI is good. Too many use it as a cop-out to (badly) hide JS payloads that make experience unusable at some later point.
1 reply 0 retweets 6 likes -
For content, interactivity means scrolling, not necessarily things like showing user account or "like button"
1 reply 0 retweets 3 likes -
Replying to @wycats @slightlylate and
You also need SSR at the primitive layer so apps built on a framework get SSR without jumping through millions of hoops.
1 reply 0 retweets 1 like
Yeah, I don't buy this line of argument. I've seen many sites adopt "SSR" and then lock up devices for 10-15s w/ script. Simply broken.
-
-
Replying to @slightlylate @wycats and
Worse, it's *invisibly* broken. There needs to be some name for this (I'm bad at names), but locking the main thread ain't cool. TTI matters
4 replies 0 retweets 1 like -
Totally agree about this. Some bad stuff you can get into, and we should make JS-powered sites more bulletproof by default.
1 reply 0 retweets 1 like - 30 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.