I'm really loving these short concept videos about things we all know because we have heard it somewhere and everyone understand the bare-bones definition of but rarely the much needed details! Another banger video.
Glad you like them! That's the main reason I'm doing these videos. Too often I'm like - "yea, I know what that is", but then, when I'm really thinking about it I realise I don't fully understand some of the basics.
Fireship clone or not, great job at explaining this subject in a concise manner with real world use-cases and easy to follow reactive visuals. We need more creators like you
0:40 I guess this visualization of current stack execution can confuse some people. You have several functions in queue and in the stack and it looks like node can pick several functions from queue and execute them sequentially at once (at one loop cycle). But the stack is actually just one function from queue.
@@awesome-coding your illustration is fine. sometimes a function will call other functions, or even itself recursively. The call stack can hold other execution context's in this way. Granted, I understand @couragic's valid concern about confusing some people. Overall, nice video! Best wishes to the both of you.
Hey! I did a Web Components related video recently which might be of interest to you - ua-cam.com/video/Jy0dMy2qDMo/v-deo.html Also, I can break down web components in a separate video for certain! Thanks for the suggestion!
Oh god another fireship rip off
Is it the best rip off though?
that was a great explanation, thanks@@awesome-coding
@@БогданТкаченко-ч5з Glad it was helpful!
Spicy European flavor Fireship
@@awesome-coding Best one yet.
The way you’ve just managed to explain a topic from scratch without making any part of it cryptic is something this space needs!
Thank you! I'm glad you found this useful!
8 years experience and damn, this is the best explanation of non-blocking I've seen
Thank you! I'm glad you found it useful!
I'm really loving these short concept videos about things we all know because we have heard it somewhere and everyone understand the bare-bones definition of but rarely the much needed details!
Another banger video.
Glad you like them!
That's the main reason I'm doing these videos. Too often I'm like - "yea, I know what that is", but then, when I'm really thinking about it I realise I don't fully understand some of the basics.
this video deserves a trillion likes, soooo concise and soooo clear and easy to understand
Thank you!
Great work on the presentation, using a real world example always improves the understanding!
Thank you for your feedback!
Fireship clone or not, great job at explaining this subject in a concise manner with real world use-cases and easy to follow reactive visuals. We need more creators like you
Much appreciated!
Hey Great Video! Finally I understood the proper use-case for this. Thanks!
Glad it helped!
Great video! This is an excellent introduction to workers
Glad you think so! Thank you!
Thanks for the explaining event loop!
Glad it was helpful!
perfect explaination. Keep up the good work brother
Much appreciated!
what a hidden gem, thank you so much!
Glad you like it!
Thank you, mate! That's the best explanation
Another awesome video! Great visuals, too
Thank you! Cheers!
That helped me, thanks for such an awesome and practical explanation!
Glad it helped!
0:40 I guess this visualization of current stack execution can confuse some people. You have several functions in queue and in the stack and it looks like node can pick several functions from queue and execute them sequentially at once (at one loop cycle). But the stack is actually just one function from queue.
This is a very good point! Thank you for mentioning it!
@@awesome-coding your illustration is fine. sometimes a function will call other functions, or even itself recursively. The call stack can hold other execution context's in this way. Granted, I understand @couragic's valid concern about confusing some people. Overall, nice video! Best wishes to the both of you.
This was awesome explanation
This type of content is the best
Thank you!
Clear explanation! thanks so much!
Glad it was helpful!
Awesome video, waiting for next one
More to come! Thank you!
Thanks for these beacons of knowledge.
short and excellent
Thanks, it was pretty good explanation!
Glad it was helpful!
Thanks! Good explanation
Glad it was helpful!
great explanation thank you
Glad it was helpful!
very good video, thank you!
Glad you found it useful!
Thanks!
Enlightenment, thanks
Glad you enjoyed it!
How about async?
Async / await is just sintactic sugar on top of the Promise API - so this is just the usual Event Loop.
What do you recommend Web Workers or WASM ?
It depends on the use case. I'd go with web workers if possible because of the simplicity. WASM usually implies adding another language in the mix.
very nice
YOU ARE SO FUCKING AWESOME, THANK YOUUUUUUUUUUUUUUUUU
Glad you found this useful! ✌️
what a nice video
Thanks!
Nice and short
Can you make a video about web coponents ?
Hey!
I did a Web Components related video recently which might be of interest to you - ua-cam.com/video/Jy0dMy2qDMo/v-deo.html
Also, I can break down web components in a separate video for certain!
Thanks for the suggestion!
@@awesome-coding wow thank you, I didn't expected a response
The challenge would be to pass functions to worker
great
Yay
Just JavaScript being javascript. Mf, someone tell me is it single threaded or not.
Like #42 :)
the answer to the Ultimate Question of life, the universe and pretty much everything
@@awesome-coding :) took 7.5 milliion years to find out!
@@AlexanderSuraphel That's like 10 seconds in JavaScript time!
Nicely done
Thank you! Cheers!