You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Remix is a very good framework! I am very excited to have encountered it and to be in touch with the future of the web.
Remix is able to load pages very fast due to nested-routes and Outlet components, which save resource loading when navigating.
However, since a first-time user needs to fully load the page document, if the nested routes contain slow-loading parts, the whole page will be affected and load slowly.
Using a cache, it is possible to return documents quickly, but it is not suitable for personalized content, and the purging of the cache upon release must be taken into consideration, resulting in a trade-off between user experience and development experience.
Next.js now supports SSR-streaming with the recent release of v12 (still in alpha).
When this is applied, the server returns the document without waiting for the rendering of the component, which takes time to load the data, and streams the incremental data after the rendering is complete. Nextjs SSR-streaming demo
I'm wondering if we can take Remix to the next level with a solution similar to SSR-streaming. I'd like to hear your (and core members' if possible) thoughts on this and whether it's feasible in actuality.
It would be great if you could choose whether or not to stream to an Outlet component like this. <Outlet stream />
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Remix is a very good framework! I am very excited to have encountered it and to be in touch with the future of the web.
Remix is able to load pages very fast due to nested-routes and Outlet components, which save resource loading when navigating.
However, since a first-time user needs to fully load the page document, if the nested routes contain slow-loading parts, the whole page will be affected and load slowly.
Using a cache, it is possible to return documents quickly, but it is not suitable for personalized content, and the purging of the cache upon release must be taken into consideration, resulting in a trade-off between user experience and development experience.
Next.js now supports SSR-streaming with the recent release of v12 (still in alpha).
When this is applied, the server returns the document without waiting for the rendering of the component, which takes time to load the data, and streams the incremental data after the rendering is complete. Nextjs SSR-streaming demo
I'm wondering if we can take Remix to the next level with a solution similar to SSR-streaming. I'd like to hear your (and core members' if possible) thoughts on this and whether it's feasible in actuality.
It would be great if you could choose whether or not to stream to an Outlet component like this.
<Outlet stream />
Beta Was this translation helpful? Give feedback.
All reactions