Don't Go Chasing Waterfalls

A deep-dive stream transcript exploring waterfall patterns in web development. Covers what waterfalls are (sequential resource/data fetching), the difference between parallel and sequential requests, and how grouping requests on the server vs. client affects performance. Discusses how client-side code splitting forces data hoisting in routers like Remix and SolidStart, why client state cannot drive server component data fetching, trade-offs of single-flight vs. parallelized data fetching, and how React Server Components handle serialization of props regardless of client visibility. Also touches on edge deployment trade-offs, streaming with Suspense, and why waterfalls are arguably the single biggest web performance issue.