Prerequisites
Describe the Feature Request
i've found that someone else has already created an issue requesting the feature request for the qwik support but he they haven't explained why nor what benefit would supporting qwik provide anyways so hopefully ill be able to get some attention to it again
Describe the Use Case
so what qwik brings to the table is it's new method of rendering called resumeability, unlike other frameworks that rely on hydration where the app is rendered twice, once on the server and once on the client, qwik renders the app once on the server and the app simply resumes on the client, but i imagine apps wont benefit much from this due to them being downloaded fully?
well another major point that i think devs would love is automatic lazy execution and lazy loading, i imagine startup performance would be a lot better and the performance hit on larger apps to be almost none due to qwik innate way of handling lazy execution of code only on demand, so that so not all the code is executed right away, instead the service worker which is smart enough to guess which Ui element is more likely to get used more and therefore priorities it when prefetching it and also the lazy loading of such code, that is the code is only executed when the user needs it, and the best part is that this is automatically done for the developer and doesn't need any extra work which is a huge DX improvement i would say from what I've experienced first hand, I've yet to test it but i imagine web view 2 apps on android would get a decent performance boost that they need.
Describe Preferred Solution
No response
Describe Alternatives
No response
Related Code
No response
Additional Information
No response
Prerequisites
Describe the Feature Request
i've found that someone else has already created an issue requesting the feature request for the qwik support but he they haven't explained why nor what benefit would supporting qwik provide anyways so hopefully ill be able to get some attention to it again
Describe the Use Case
so what qwik brings to the table is it's new method of rendering called resumeability, unlike other frameworks that rely on hydration where the app is rendered twice, once on the server and once on the client, qwik renders the app once on the server and the app simply resumes on the client, but i imagine apps wont benefit much from this due to them being downloaded fully?
well another major point that i think devs would love is automatic lazy execution and lazy loading, i imagine startup performance would be a lot better and the performance hit on larger apps to be almost none due to qwik innate way of handling lazy execution of code only on demand, so that so not all the code is executed right away, instead the service worker which is smart enough to guess which Ui element is more likely to get used more and therefore priorities it when prefetching it and also the lazy loading of such code, that is the code is only executed when the user needs it, and the best part is that this is automatically done for the developer and doesn't need any extra work which is a huge DX improvement i would say from what I've experienced first hand, I've yet to test it but i imagine web view 2 apps on android would get a decent performance boost that they need.
Describe Preferred Solution
No response
Describe Alternatives
No response
Related Code
No response
Additional Information
No response