Qwik framework overview (Miško Hevery)

[@jhadesdev9576]

Hello Misko, Qwik seems super interesting, thank you for sharing. 👍 So change detection works by using the bind: syntax and document.querySelectorAll? If a component triggers an event and it's binded to other components, querySelectorAll will query the DOM to find all the components that need to be re-rendered, is this how it works? And of course, the million dollar question that developers always love, how far do we think we are of version 1? 😊 Again thank you for sharing, I'm looking forward to learn more about Qwik 👍

[@RasmusSchultz]

Talking about other lazy loading strategies, "none of that stuff really works" seems pretty dismissive. Chunking doesn't work? Import statements don't work? Structuring a large application into modules that get loaded when you access a menu or tab doesn't work? It may not have worked for you. But it worked and continues to work for plenty of projects. Frankly, I'm not at all convinced that issuing another web request for another bit of code for literally every button or checkbox is going to be a net win - the sheer amount of requests per user is going to put some serious load on your servers. This type of tech might be appropriate for a certain type of project, but I can't see this becoming the "next big thing".

[@jamesbarrow]

What if these requests are using a protocol that supports streaming the scripts down in parallel over a connection that isn't closed? And perhaps the prefetching of resources is good enough to predict those required dependencies as well to bulk them together