EPISODE · Apr 1, 2020 · 1H 28M
Does route-based code splitting make UX worse?
from Frontend First · host Frontend First
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)
Embed this episode
What this episode covers
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.
Ready to play
Does route-based code splitting make UX worse?
No transcript for this episode yet
Similar Episodes
No similar episodes found.
Similar Podcasts
No similar podcasts found.