4 ms·
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
by 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.