You basically explained why I haven't jumped on the bandwagon of these "post-react" frameworks. The jump in technology is big enough yet to warrant a switch. Qwik on the other hand presents a true paradigm shift that can provide some real benefits to the end user.
Dude I waited for nuxt 3 to learn vue3, js, nuxt3, and now I'm having second thoughts before I get started. I'm not sure if theit new hybrid setup is just half a quik when it comes to performance or any other configuration, don't want to take something on if it don't need it. Is react exclusive to quik? (Learn react now because it's needed? Svelte actually looked cool since I'm fresh out of gate learning js, will it work with quik? What do you think? Will other frameworks eventually do or are they already doing similar things as quik or working on it which would make it redundant? Is it framework agnostic, or is it based on reacts stack? Any insights appreciated, if quik is the only one doing something like this I gotta get the right pieces in place around it. Cheers
This explained hydration and reconciliation really well and I think I understand that. But I did not at all get a satisfying explanation of resumability. I went back and rewatched that part twice. Seems like it wasn't actually described.
I haven’t done DD as I’m learning myself but I think in his example, what he’s trying to convey is the page is loaded in the past and the html is cached with minimal hydration (my guess) and we only need to download the missing js ( please correct if im wrong )
Ok, what I see here is too much bloat, too much tooling bloat, too much hand shaking bloat, yes all of this looks great in our super fast developer laptops with 32-64GB of RAM to compile assets with npm because with less RAM npm crashes. Reminds me of Rick Sanchez "is like slavery with extra steps" Does anyone remember GWT? Google Web Toolkit that is a Java library and compiler to make your entire site in Java and the compile parts to super fast minimized javascript using ClosureJS library. So you could have your server & browser logic without repetition. And it had server side rendering. Honestly, I prefer the Past.
Thank you for the first real explanation of hydration that I’ve found
Thank you for making this so clear.
You basically explained why I haven't jumped on the bandwagon of these "post-react" frameworks. The jump in technology is big enough yet to warrant a switch. Qwik on the other hand presents a true paradigm shift that can provide some real benefits to the end user.
Dude I waited for nuxt 3 to learn vue3, js, nuxt3, and now I'm having second thoughts before I get started. I'm not sure if theit new hybrid setup is just half a quik when it comes to performance or any other configuration, don't want to take something on if it don't need it.
Is react exclusive to quik? (Learn react now because it's needed?
Svelte actually looked cool since I'm fresh out of gate learning js, will it work with quik?
What do you think? Will other frameworks eventually do or are they already doing similar things as quik or working on it which would make it redundant?
Is it framework agnostic, or is it based on reacts stack?
Any insights appreciated, if quik is the only one doing something like this I gotta get the right pieces in place around it. Cheers
That was super helpful and detailed, thank you so much
This explained hydration and reconciliation really well and I think I understand that. But I did not at all get a satisfying explanation of resumability. I went back and rewatched that part twice. Seems like it wasn't actually described.
I haven’t done DD as I’m learning myself but I think in his example, what he’s trying to convey is the page is loaded in the past and the html is cached with minimal hydration (my guess) and we only need to download the missing js ( please correct if im wrong )
Great explanation, thank you!
This was super useful, thanks
Excelent video! Thanks !
best explaination ever
Great!
Great explanation
My guy needs to mute slack 😢 great vid though ☺️
An amazing explanation. Do you do any courses?
how does qwik compares to marko?
So resumability has a bunch of network calls for all those tiny bits of JS. Seems bad
Just open the slack bro
Ok, what I see here is too much bloat, too much tooling bloat, too much hand shaking bloat, yes all of this looks great in our super fast developer laptops with 32-64GB of RAM to compile assets with npm because with less RAM npm crashes. Reminds me of Rick Sanchez "is like slavery with extra steps"
Does anyone remember GWT? Google Web Toolkit that is a Java library and compiler to make your entire site in Java and the compile parts to super fast minimized javascript using ClosureJS library. So you could have your server & browser logic without repetition. And it had server side rendering.
Honestly, I prefer the Past.
Ehhhh this is more to do with servers too. Not just CSR
Thank you, but you didn't explain it well.
I cant believe I had a hard time understanding this before