Miško Hevery on Qwik versus React

👉 I'm a host on the React Round-Up podcast: devchat.tv/pod...
👉 Don't forget to subscribe to this channel for more updates: bit.ly/2E7drfJ
👉 Discord server signup: / discord
👉 VS Code theme and font? Night Wolf [black] and Operator Mono
👉 Terminal Theme and font? oh-my-posh with powerlevel10k_rainbow and SpaceMono NF

[@lukeinderwick5951]

Absolutely loving these interviews, especially when you take what the interviewee has said and explain it in a more digestible way for us normies. Giving real world examples of what was just said is incredibly helpful for making sense of something complicated. Great job! 👍

[@444ous]

Really cool interview! So funny to see a slightly nervous Jack xD But who wouldn't be, next too an amazing guy like Miško

[@jaymartinez311]

I’m just waiting on the full course from your channel and I can take over the world 😂 I like the one you did before but I need to know more auth and just a bunch of other stuff. Would be nice if you did a video comparing managing state in qwik vs react. Big thank you for everything you do!

[@jherr]

Thanks! One of the nice things about Qwik is that it has really good state management primitives like signals built in. So you don't need to bring in a state manager. You just don't need it. Same thing with Solid.

[@jaymartinez311]

@@jherr aaah ok. I did not know that. It would be a great video to make about how qwik handles rerenders vs react. If qwik even rerenders at all since I guess from this video there is no hydration. Learn a lot I have to look up in this interview. Always love and respect to you and your family. Have a blessed day 🫡

[@jherr]

@@jaymartinez311 It does re-render when you update state on the client. On a case by case basis it decides between either a VDOM based update like React, or a direct update similar to Million-Js or Angular's Ivy.

[@jaymartinez311]

@@jherr oh ok. Thanks again

[@admiralicic]

Really nice, definitely got me motivated to try it :)

[@AlazTetik]

Great talk! 🎉😊❤

[@RolandAyala]

Qwik is amazing and love the resumable model -- very innovative, and glad to see discussion here about serialization benefits because too much emphasis on faster page load times IMO. I found Qwik to be a very well thought out framework that's a joy to use, and the experience of its creators shines through in the design details. Ecosystem is still lacking though by comparison to React (as is also true for Svelte and Solid) and I see a lot of folks downplaying importance of, so for now I'm needing to stay on React (w/ Remix).

[@IainSimmons]

Great interview! Both you and Misko are really good at explaining things and connecting to examples. One thing that I wasn't sure about, Misko said you don't need to annotate anything in Qwik, but don't you need to add the $ everywhere and use their component$ and onClick$ and all that? That certainly looks like annotation to me!

[@alexhutsanovich2153]

It is a very interesting interview opening new view. ❤

[@PepePlaca-t6s]

amazing talk. great content!

[@patrickstubner1712]

Thanks Jack, love it. What about QWIK and Module Federation?

[@jherr]

That's an interesting question. I'm not sure that Qwik would do well in a very simple implementation of Module Federation. But I do think Qwik as a solve in the MFE/Island space could be very intersting.

[@martinemanuel8239]

this guy just fixed the web

[@PepePlaca-t6s]

hahaha so true, so natural and intuitive for both dev and user

[@greendsnow]

So does qwik eat up my edge minutes or not?

[@jherr]

As with any SSR platform, yes, you are going to be doing compute to build the initial state of the page.

[@greendsnow]

@@jherr yes but qwik seems to be consistently making requests to the server for small bits. 1 million requests costs $2 in Vercel, whether it's 1ms or 50ms. With SSR you don't do that many requests

[@jherr]

@@greendsnow I see what you are saying, and yes, it is making requests for "small bits". But those small bits are actually just portions of a static JS bundle that would be CDN deployed. It's not making small bits requests for dynamic content. All the SSR stuff, including all the data requests, is done by the time the page makes it to the browser. After that the extra requests are for the JS to drive portions of the page, which are only requested as needed.

[@greendsnow]

@@jherr that's still a trade off. I think we need an nginx benchmark for people who are self hosting qwik. I wonder how many requests will be denied, which means a broken experience in qwik

[@jherr]

@@greendsnow So what does "self hosting" mean? Because there are lots of CDNs and lots of deployment pipelines handle the CDN deploy of static assets like JavaScript bundles. So if "self hosting" means serving static assets off of a node server then IMHO that's just not deployed correctly. And in order for a JS bundle request to be denied that would mean there was an issue in deployment, or the CDN was down, and if Cloudflare CDN, Akamai, or Cloudfront is down... that's gonna be a bad day for the Internet. I'm not defending Qwik really, use it or don't, I do think there are some issues, like the overall complexity of the approach versus something like non-RSC React, I just don't think this particular issue is a Qwik killer. IMHO.