Why everybody needs to use a framework
summary
Claim: use a framework; demonstrates by building one from scratch with Express and Vite, converting a client app into full server-side rendering that serves dog-breed data, moving client fetches into exported server functions and wiring file-system routing plus getServerSideProps style APIs. The demo replaces synchronous renderToString with renderToPipeableStream to enable streaming and hydration, it runs end-to-end, and it surfaces scaling and tooling pitfalls of DIY server-component workflows.
AI-written summary · about
chapters (11)
- 0:00Welcome
- 1:05Frameworks for developers
- 2:50Libraries vs frameworks vs meta frameworks
- 5:37What frameworks do
- 8:05Building a framework demo
- 13:26Adding server-side rendering
- 18:22Data fetching in frameworks
- 23:02Fixing server rendering
- 26:54Future of frameworks
- 31:09Should you use a framework
- 32:12Q&A
