Qwik: No hydration, auto lazy-loading, edge-optimized, and fun

Re:Qwik: No hydration, auto lazy-loading, edge-optimized, an... by mpeg on Thursday October 13, 2022 @01:10AM (#33187486)

I'm not sure why you think MPA is somehow inherently slower than a SPA

For a complex application, data has to load in from the server on every page load – it can't simply be all bundled into the js.

In eBay's case, a MPA using their own custom framework makes sense, as they do async rendering (e.g. you can load and show the most important data in the page quickly, while ancilliary stuff can load afterwards) and partial hydration (so if a component doesn't require js, no js loads/runs)

[ Parent | on HN ]

Re:Qwik: No hydration, auto lazy-loading, edge-optimized, an... by aatd86 on Thursday October 13, 2022 @10:40AM (#33191630)

I haven't said that.

The point is that hydration is more of an issue for MPAs since each time the page loads (on navigation), the html must be parsed and DOM objects need their javascript listeners attached.

For SPA, this is not the case after the initial page load event. Hydration needs to happen only once at startup.

[ Parent | on HN ]