Twitter | Search | |
This is the legacy version of twitter.com. We will be shutting it down on 15 December 2020. Please switch to a supported browser or device. You can see a list of supported browsers in our Help Center.
Addy Osmani
2019 wishlist for a React framework 🤞 📦 Small initial vendor bundle ✂️ Automated code-splitting (route/component) 💰 JS perf budgets (dev/prod) ⚡️ Constraints to stay on the fast path 🍽 Differential bundling ES2015+ 💄 Extract & optimize CSS 🚿 Progressive hydration for SSR
Reply Retweet Like More
tom byrer 29 Dec 18
Replying to @addyosmani @GatsbyJS
Reply Retweet Like
Addy Osmani 30 Dec 18
Replying to @tombyrer @GatsbyJS
Next & Gatsby do a *great* job trying to help out of the box (e.g Next's FS-based page splitting, Gatsby prefetching). There's still quite a bit we can do here for easy-peasy guaranteed perf on mobile. Looking fwd to working more on this problem space w/folks :)
Reply Retweet Like
Pavel Klimashkin 30 Dec 18
Replying to @addyosmani
What do you mean by 'Extract and optimize CSS'? React is, thankfully, css agnostic. Or, by calling React a framework you expect it to start including everything out of the box next year?
Reply Retweet Like
Addy Osmani 30 Dec 18
Replying to @p_klimashkin
I’m distinguishing between React (the core library) and React frameworks (like Next.js). I would like to see opinionated abstractions explore solutions to some of these other problems. Core’s doing great enabling work via React.lazy(), Suspense etc
Reply Retweet Like
tim arney 30 Dec 18
Replying to @addyosmani
Where can I find out more about what differential bundling is?
Reply Retweet Like
Addy Osmani 30 Dec 18
covered part of this in his deloying ES2015+ code write-up wrote about it in
Reply Retweet Like
Andrew Ray 30 Dec 18
Replying to @addyosmani @Vjeux
Does Next.js satisfy these criteria?
Reply Retweet Like
Addy Osmani 30 Dec 18
Replying to @andrewray @Vjeux
Today Next.js handles automated code-splitting (with their pages pattern) but the other items (like budgets, constraints etc) are still ideas I would love to see considered.
Reply Retweet Like
Gaurav Gupta 30 Dec 18
Replying to @addyosmani
What exactly is progressive rehydration and why is it required? Does client side hydration for SSR code take too much time? Couldn't find a lot of info while googling, (someone) care to explain in brief?
Reply Retweet Like
Addy Osmani 30 Dec 18
Replying to @gaurav5430
On mobile, we often see multi-second delays between first contentful paint and time to interactive for apps where SSR + CSR via hydration is used (as the main thread is busy processing script). Progressive hydration avoids a full teardown/rebuild as you limit what to rehydrate
Reply Retweet Like