Listen "Does route-based code splitting make UX worse?"
Episode Synopsis
Sam and Ryan talk about the tradeoffs between shipping a single bundle of code vs. the route-based code splitting approach used by many tools like Gatsby and Next. They also talk about their recent experiences building with React, and whether web developers should compete with native experiences or embrace what the web has to offer. Topics include:- 2:38 – In React, there are no components- 13:45 – The feeling of momentum in React- 23:33 – SPA bundles vs. per-page code splitting- 45:33 - Conceptual code splitting, and web experiences vs. native experiences- 1:06:30 – React.Children utilities Links:- [Domain Modeling with Mirage JS training](https://www.youtube.com/watch?v=lfDBb0Ar-rc)- [Mirage JS Inspector Livestream 1](https://www.youtube.com/watch?v=WTDj7MXzejc)- [Mirage JS Inspector Livestream 2](https://www.youtube.com/watch?v=odcfQAwYGrc)- [Mirage JS Inspector Livestream 3](https://www.youtube.com/watch?v=knSI60CTZ-U)
More episodes of the podcast Frontend First
Creating a background gradient from an image
12/12/2024
Exploring useActionState
14/11/2024
Can you self-host Next.js?
10/10/2024
Tom Occhino on the future of React
18/09/2024
Render props
05/09/2024
Controlled and uncontrolled components
28/08/2024
Unstyled React components
15/08/2024
What is a framework?
01/08/2024
ZARZA We are Zarza, the prestigious firm behind major projects in information technology.