Does route-based code splitting make UX worse?


Manage episode 257554721 series 1635850
由Player FM以及我们的用户群所搜索的Frontend First, Sam Selikoff, and Ryan Toronto — 版权由出版商所拥有,而不是Player FM,音频直接从出版商的伺服器串流. 点击订阅按钮以查看Player FM更新,或粘贴收取点链接到其他播客应用程序里。

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


- [Domain Modeling with Mirage JS training](

- [Mirage JS Inspector Livestream 1](

- [Mirage JS Inspector Livestream 2](

- [Mirage JS Inspector Livestream 3](