294 karma · joined April 11, 2019
AFAIK Qwik would have a similar initial load time to other server-side rendered frameworks where all you send across the wire first is the HTML and CSS to render that particular page. That's the initial page load.
From there it loads the JS which then hydrates data and turns it into a functioning React app. So what Qwik claims to improve over other solutions is the time-to-interactive metric, rather than the initial page load. Is this a correct assessment?
If so, then the "100ms -> 1% more conversions" buy line does not seem to really follow on from the actual improvements of Qwik over other methods. Anyone understand this more than me?
For example: 1) selecting a checkbox alters other fields in the form 2) validation that needs to hit the backend and then present warnings/errors to user 3) field arrays -> sending back a list of fields
The best guess for why this is that I've seen online is that it's because they're targeting younger age brackets more aggressively and kids love to rewatch the same things over and over.