|
|
|
|
|
by aatd86
1343 days ago
|
|
What I do not understand is why is hydration claimed to be such a concern if it only happens on initial page load and then the client-side takes over? In Amazon famous case, the 100ms delay was because it was an MPA: each page change was a page load. In that case I'd understand. |
|
However, there are teams that have a lot of insight into the needs of ecommerce that are investing heavily in reducing the hydration overhead – I imagine the reason for it is that in very dynamic sites it feels clunky that the user can't interact with the page until it has hydrated.
It is no coincidence that the only other framework besides Qwik that is being built around resumability is eBay's Marko 6