Document hydration and hydration issues for dioxus fullstack
ealmloff opened this issue · 2 comments
We briefly mention hydration in the choosing a web renderer chapter, but we don't explain it in the fullstack guide. We should explain both hydration and how to recognize and avoid hydration errors (nondeterminism).
In the meantime - can you tell me please, what strategy/implementation model is Dioxus inspired by? Or heavily based on?
Just to give me better mental model to some already existing, described system.
For example, is it something like Qwik handlers? Or more like Next.js (expensive) hydration, or React server components.... ?
In the meantime - can you tell me please, what strategy/implementation model is Dioxus inspired by? Or heavily based on? Just to give me better mental model to some already existing, described system. For example, is it something like Qwik handlers? Or more like Next.js (expensive) hydration, or React server components.... ?
It is similar to (how I understand) hydration in Next.js works. Every component is run on both the server and the client unlike Qwik and server components. Hydration should be faster than Next.js because we use the structure of templates to only hydrate dynamic elements in your site. In the Javascript world, I think millionjs does something similar to speed up hydration