Awesome show guys ! I give my two cents about the big red button, as an Angular guy, it's the changeDetection strategy, it's default to the bad strategy, and only after some time you learn that you should go with the good strategy 😅 Cheers guys, go Qwik 💙
Question: 1:14:44 The server$ function defined on line 98: Normally I would avoid defining functions inside of other functions because it would be re-created on every call. Does Qwik avoid this problem (because of the compiler step - which would extract that function into its own file so it no longer is re-created every call)? Or would it be more optimal to define that function maybe in the component scope (or define the function outside the component scope, and pass in the signal rather than trying to use it directly)? In the current code, does the server function get re-created every time filter.value changes (like useComputed would re-calculate)? Or is it able to just get the updated filter.value when it runs?
I asked Miško and he said, "No need to pull functions out. Any function which is wrapped in $ is automatically memoized. So there is no benefit to pulling them out."
@@learnwithjason Thanks! Very cool, one less thing to think about! None of this "re-create all the functions every time the component renders or a function fires" stuff! Cheers!
what about the difference with signals of preact and like maybe having some react component along the way if we want to import a react librairy/pkg or using Astro instead with qwik and react ?
great questions! I have Steve Sewell joining next month to teach us about Qwik + Astro and I think he'd be better qualified to answer. details will be posted on lwj.dev if you want to mark your calendar and join live to ask him!
The execution model is interesting, but does seem like we're trading "fast perf defaults" for some "strange footguns during dev that'll frustrate you to bits". For instance, that API RequestHandler not letting you do a "return json(...)" in favour of void returns - interferes with my muscle memory from years of doing Express.js with early the return pattern to avoid nested conditionals. And empty returns feel weird: { json(...); return; }
Qwik is missing only one thing that other modern frameworks (svelte, solid) = global store that will make it unnecessary to create and use external libraries for global state
@learnwithjason difficult to judge. React has context, yet state management libraries are very strong in this environment. The question is whether the context in Qwik has similar limitations as the react context?
I don’t like dual stream setups because the comments sections are split and that gets weird. but I have been wondering about whether I should switch over to YT for the live streams. not sure, really
![เป็นไปได้ไหม - WanMai [Performance Video]](http://i.ytimg.com/vi/Eh5hItD4Mr0/mqdefault.jpg)
this guy is very smart it was great to listen to both of you talk
This for me is beyond amazing!!!! Thanks Misko!!! Thanks Jason!!! This changes the entire game where the state is stored in the html and resumablility
Great to see you invited Misko again. Let's build resumable apps 🏎 ✌
Edit: don't worry Jason, you passed the Qwik tech interview 😎
lol thanks! 😅
Awesome show guys !
I give my two cents about the big red button, as an Angular guy, it's the changeDetection strategy, it's default to the bad strategy, and only after some time you learn that you should go with the good strategy 😅
Cheers guys, go Qwik 💙
This is mind blowing, great job Miško and the team 💪
Thank u Jason and Misko , ur awesome guys :)
I'm very excited for Qwik. Beyond cool
Question: 1:14:44 The server$ function defined on line 98:
Normally I would avoid defining functions inside of other functions because it would be re-created on every call. Does Qwik avoid this problem (because of the compiler step - which would extract that function into its own file so it no longer is re-created every call)? Or would it be more optimal to define that function maybe in the component scope (or define the function outside the component scope, and pass in the signal rather than trying to use it directly)? In the current code, does the server function get re-created every time filter.value changes (like useComputed would re-calculate)? Or is it able to just get the updated filter.value when it runs?
I asked Miško and he said, "No need to pull functions out. Any function which is wrapped in $ is automatically memoized. So there is no benefit to pulling them out."
@@learnwithjason Thanks! Very cool, one less thing to think about! None of this "re-create all the functions every time the component renders or a function fires" stuff! Cheers!
Qwik is really interesting .. I've made a few toy projects in it last week.
what about the difference with signals of preact and like maybe having some react component along the way if we want to import a react librairy/pkg or using Astro instead with qwik and react ?
Qwik and Astro work together as of a few weeks ago, so I think you can do what you mentioned now!
@@learnwithjason would have been nice to simply just use qwik :)
and what about qwik signals (resumability ) vs Preact signals vs Signal signals?
great questions! I have Steve Sewell joining next month to teach us about Qwik + Astro and I think he'd be better qualified to answer. details will be posted on lwj.dev if you want to mark your calendar and join live to ask him!
@@learnwithjason awesome, for qwik an astro
that's it, qwik made all other frameworks obsolete now, this is fucking insane
mind blowing
The execution model is interesting, but does seem like we're trading "fast perf defaults" for some "strange footguns during dev that'll frustrate you to bits".
For instance, that API RequestHandler not letting you do a "return json(...)" in favour of void returns - interferes with my muscle memory from years of doing Express.js with early the return pattern to avoid nested conditionals.
And empty returns feel weird:
{
json(...);
return;
}
How does Qwik perform on high latency network connections?
Qwik is missing only one thing that other modern frameworks (svelte, solid) = global store that will make it unnecessary to create and use external libraries for global state
would what you're looking for be possible with a top-level store and context? qwik.builder.io/tutorial/context/basic/
@learnwithjason difficult to judge. React has context, yet state management libraries are very strong in this environment. The question is whether the context in Qwik has similar limitations as the react context?
Would have loved to participate during this stream, Had some questions for Misko. Any plans to stream on youtube and twitch at the same time?
I don’t like dual stream setups because the comments sections are split and that gets weird. but I have been wondering about whether I should switch over to YT for the live streams. not sure, really
The mic does do something weird! But I think it's when you both speak
Literally black magic
Jason, were you able to sleep after this session ?