2 ms·

How does Astro hybrid rendering compare to Qwik? https://qwik.builder.io/ https://qwik.builder.io/

• SparkyMcUnicorn 4y ago
  Apparently Astro is faster. https://docs.astro.build/en/concepts/mpa-vs-spa/#case-studies https://docs.astro.build/en/concepts/mpa-vs-spa/#case-studie...
  • mixedCase 4y ago
    It seems like it's not really faster by default, if you watch how the video continues after they announce the first results. They're going out of their way to imitate the lazy-loading Qwik does by default for the parts that require heavy-lifting, once they disable that the magic's gone. They weren't, as expert frontend programmers, even 100% sure about what was causing the high scores at first and they had to go and check if it was the lazy-loading for themselves. I'd give an average dev something with the Qwik approach, where they don't have to choose and automated analytics-based PGOs can be performed. With that said they stated that the server-side rendering part of Qwik is not very optimized. I'd love to see if Qwik.js can get their SSR to perform better or if someone else (hopefully in a better language and runtime) is able to knock that one out of the park.
• Alifatisk 4y ago
  To my understanding... Astro is tries to rely on SSR as much as possible with MPA approach, so the client have to render as little JS as possible. Qwiks goal is to be instant for every device, it does this by delaying the download & execution of JS so much it can. Qwik also partially renders the content in its state on the server, then sends it over to the client to do the rest.
  • lern_too_spel 4y ago
    Qwik can fully render server-side, but if you cause an update, it downloads the minimum JS needed to make that update on the client.
    • Alifatisk 4y ago
      You’re right, but I pointed it out because resumability is one of their key features.