Splitting the Work: Streaming Server Rendering with Suspense: Shaundai Person

Splitting the Work: Streaming Server Rendering with Suspense
Many React developers use server rendering to improve performance. Before React 18, however, all four (4) steps in the server rendering process (data fetching, rendering to HTML, loading JavaScript, and hydrating) had to be completed for the entire app at once. This meant that a bigger or more complex part of your app would block other parts from moving onto the next step, making your app appear slower. Thanks to optimizations in React 18, you can use Suspense to break your app into smaller parts that go through these steps independently. Users benefit from an app that they can see sooner and interact with almost instantaneously!
About Shaundai
Shaundai is a Senior Software Engineer (Netflix) and TC39 Delegate based in Atlanta, GA, US. She is passionate about making programming interesting and approachable for all, and does that through her work as a course instructor (tsforjs.com), co-lead for React Robins (reactrobins.com), and technical blogger. In her spare time, Shaundai loves to go hiking, jogging, and listen to audiobooks. Find her on Twitter at @shaundai.
Recorded live in San Francisco at Reactathon 2023. Learn more at reactathon.com

[@oliverhughes169]

Great talk and explanation of CSR vs SSR. This seemed like a talk that could have come from the React core team, using Netflix as an example site. Since Shaundai is working at Netflix, it would have been really interesting to see (at the end of the talk) a real world example of where Netflix adopted Suspense to improve the UX of their users, rather than just the hypothetical example app with a comments section (which was great for explaining the topic).

[@aristosxanthus658]

Great explanation of CSR vs. SSR

[@PRIST.A.C]

Shaundai Person much love

[@yachujoshi]

Great Talk!!