4 ms·
I think this new wave of server-enabled React is enabling codebases that are better organized than old MVC stacks. The MVC way was: 1. Look at the route 2
by colinclerk 5y ago
I think this new wave of server-enabled React is enabling codebases that are better organized than old MVC stacks.
The MVC way was:
1. Look at the route
2. Recognize that this route has, e.g. A Header, A Sidebar, and Content
3. Load the data for the Header, Sidebar, and Content
4. Pass the data to the templating engine
5. Use the templating engine to render the route, which likely fans the data for the Header, Sidebar, and Content into individual template files.
Remix highlights that Header, Sidebar, and Content are three separate components. Instead of loading the data all at once (#2 above) and then rendering all at once (#5 above), it allows you to load and render each component individually.
- bpicolo 5y agoThis is what Facebook's Bigpipe was doing in 2010. https://engineering.fb.com/2010/06/04/web/bigpipe-pipelining-web-pages-for-high-performance/ https://engineering.fb.com/2010/06/04/web/bigpipe-pipelining...
- deleted 5y ago[deleted]
- tuan 5y ago>> load and render each component individually you can do that with Suspense. React doc calls that render-as-you-fetch pattern https://reactjs.org/docs/concurrent-mode-suspense.html#approach-3-render-as-you-fetch-using-suspense https://reactjs.org/docs/concurrent-mode-suspense.html#appro...