I mean yes but for that size I wonder if the critical path is 100% critical, as in maybe unused styles,.. are leaped in there
-
-
Replying to @JoviDeC @SpeedCurve
You should load any of the slow ones w/ devtools coverage on. It is not hopeful.
1 reply 0 retweets 0 likes -
Replying to @slightlylate @SpeedCurve
Yes, unused styles and code (for critical) have pretty high numbers which makes me have hope that we as a community could probably given these examples make tools.
1 reply 0 retweets 0 likes -
Replying to @JoviDeC @SpeedCurve
The continual addition of more tools over the past decade has not meaningfully improved the fraction of code used nor interactivity nor site availability nor bundle sizes. Why is this time different?
1 reply 0 retweets 0 likes -
Replying to @slightlylate @SpeedCurve
The focus has shifted, it doesn't seem like we have aimed for the goals you are expressing for a long time. We also didn't have the right examples/problem scenario's for a long time or less publicly. I'd rather fight the problem than report it
1 reply 0 retweets 0 likes -
Replying to @JoviDeC @SpeedCurve
Has the focus shifted? Admittedly a trailing indicator, but the rate of disasters crossing my desk has not slowed. And I hear more lipservice from the worst offenders than I observe concrete action.
1 reply 0 retweets 0 likes -
I mean, Preact and Lit and Svelte et al are chugging along, doing the good work, and we very much need them. But I don't see the React community, e.g., actually making a turn & observe no real leadership from FB on this.
1 reply 0 retweets 2 likes -
Do you have a ranked list of requests for React leadership? e.g. is your top wish to reduce the size of React itself? Or for CRA to do something? (What would you have it do, other than maybe failing production builds with large bundle sizes?)
1 reply 0 retweets 0 likes -
For years I've been begging for: - guidance re: bundle sizes & mobile in their perf docs - movement on React size - public discussion of what it takes to keep perf in line at FB (pipeline, metrics, etc.) There's more, but that would show minimal interest in the problem.
2 replies 0 retweets 2 likes -
“Movement on React size” do you mean “set a goal to be as small as Preact”? If not, how small is “small enough”?
1 reply 0 retweets 0 likes
Lemmie put it this way: if a dozen other frameworks can do what your tool does in half the size or less, how important is size to you?
-
-
I mean there are tradeoffs, essentially missing the synthetic event system can be annoying when supporting older browsers. Imo concurrent doesn't bring a lot to the table for smaller-medium applications
1 reply 0 retweets 0 likes -
Yeah,
@slightlylate are you saying, “React needs to ditch the synthetic event system”? Or just “React needs to code golf more”? The former is a pretty big request; it wouldn’t be backwards compatible.1 reply 0 retweets 0 likes - 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.