6 ms·
Qwik maintainer here, lots of good feedback for our landing page! we already updating much of the content there. Please check this 20min if you wanna understand
by manucorporat 4y ago
Qwik maintainer here, lots of good feedback for our landing page! we already updating much of the content there. Please check this 20min if you wanna understand of the fundamental building block that makes this framework so different: https://www.youtube.com/watch?v=BxGbnLb5i9Q https://www.youtube.com/watch?v=BxGbnLb5i9Q
A lot good content here too: https://qwik.builder.io/media/ https://qwik.builder.io/media/
- kolme 4y ago¡Hola, tocayo! Mind if I ask you a Question? I've seen a talk of yours about Stencil and how it was compatible with other things because of Web-Components. How is the compatibility of qwik with Web-Components? Cheers.
- dogoku 4y agoI am also interested in hearing your opinion on this, especially since you are one of the creators of Stencil. We jumped into stencil with the idea that web components are the future and that we'd be able to build once and use across multiple frameworks. The latter has been true, but challenging (mainly due to react's quirks) but the former is what worries me. I can see this trend of moving away of SPA and into highly optimized SSR techniques, like Qwik's resumability, but they contradict the "cross-framework", "use the platform" nature of web components. For example, is there any way for the Qwik compiler to know if a 3rd party custom-element is interactive and determine when or if it needs to send down the custom element definition?