I think that it's wrong to blame React, because that isn't the conversation. It's not wrong to observe that people assume that React is "fast enough" and that there's too little discussion about techniques that should come default across the board.
-
-
Replying to @wycats
Also, I don't "blame" React. Instead I note the probability (approaching 1) that sites with 400K of 1P JS include a relatively heavy framework, too many polyfills, and many other unneeded elements. Heavy FW use is a symptom of broken culture and management priorities.
2 replies 0 retweets 10 likes -
Replying to @slightlylate @wycats
Adam Rackis Retweeted Adam Rackis
Define heavy? React is < 10% of that 400K. If you really want to make this better, *here's* the battle to be fought:https://twitter.com/AdamRackis/status/1040029445179039744 …
Adam Rackis added,
3 replies 1 retweet 14 likes -
Replying to @AdamRackis @slightlylate
The thing in your cited tweet is a big piece of what my other tweets were getting at! STRONG CONFIRM!
2 replies 0 retweets 8 likes -
Another piece is figuring out how to model async fetching in frameworks so that simply using popular routers in the normal way gets you a decent amount of code splitting.
2 replies 0 retweets 3 likes -
Replying to @wycats @AdamRackis
The best tools are already shipping solutions: https://sapper.svelte.technology/guide#routing https://polymer.github.io/pwa-starter-kit/configuring-and-personalizing/ … https://nextjs.org/docs/#automatic-code-splitting … https://ionicframework.com/pwa/toolkit https://github.com/developit/preact-cli … etc. etc.
3 replies 2 retweets 10 likes -
Ooo, Vue is a prime example of this. Allow component to component registrations to accept `() => import()`, allow routes to accept `() => import()`, anywhere you import modules for your framework, should also have the capability to wire up those same dependencies w/ `import()`.
2 replies 1 retweet 10 likes -
-
Replying to @dan_abramov @TheLarkInn and
This is roughly the Wiz approach (the big internal Google framework). Lots of room for different strategies to atomize!
0 replies 0 retweets 2 likes -
This Tweet is unavailable.
I make exactly this point in the article if you read to the end: https://infrequently.org/2018/09/the-developer-experience-bait-and-switch/ … It is worth saying, though, that when this is the case an analysis about performance should disclaim this deviation from the global baseline.
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.


