💙 Twitter: twitter.com/realDevSage 📙 Ebooks: payhip.com/devsage 💥 Discord: discord.gg/BP8wPv6raA 👕 Merch: cottonbureau.com/people/devsage

Your way of explaining is probably the best I've seen on KZfaq. Your video on a certain concept pretty much leaves me with no questions to ask about it.

I love your approach of explaining in a short consice and a simple manner. Thank you now I have an understanding of web workers. ❤️

A lot of these videos have been super helpful! Good length, good explanations. Thanks dude! Keep it up!

Best explanation I've heard yet. I'm ready to code some workers now. 👍

Short and to the point. Great explanation thanks man. new subscriber notification up.

clear and informative with an example. Thank you so much.

Thank you man, it was an intro of basics , but it was useful, it introduced me to the main concept of Web Worker API

this is so helpful especially for a beginner

Feels lucky I discovered your channel

Wow this is a great tutorial. I have seen like 20 videos of you in last 2-3 hours, your explanations are super easy to understand. Can you please also make a video on use cases distinguishing web worker vs service worker and web scokets? I am confused which one to be used for what type of use cases?

Nice example demo. Works perfectly.

You Sir are a true hero. Thanks for this!

I've never heard about web workers before, this is interesting, thank you so much.

you just earned yourself a subscriber. well done!

Simple and Perfect Keep it up!!

Very clearly explained! Thank you for sharing.

Thank you. Very well explained 👍

Simple, Short and Clean 👍👍👍

Thank you for explaining this. It was very helpful!

That was sooooooooo clear and straight . Thank you very much

Brilliantly explained, thank you!

super awesome explanation, man 👍👏

So very well explained, thanks.

Nice job boy , Thank you so much 🌹

Good work man, it really helped

Yep - great stuff - subscribed.

Very lucidly explained!! Thank you....

What if you need web workers to do multiple tasks and in different js files, how will they distinguish between msgs they pass among themselves. Like there is no indication apart from where it's called an instance of worker can have different name, but inside worker.js file how will they distinguish between multiple functions (performing different tasks)

Great explainer video. Loved the way you demonstrated. For your next videos can I request some things I often confuse with "web workers"? Service workers Web sockets Web components

great, I wonder if i can inject worker as code from server to hide my logic from public but still using client computation power

Great video. Thanks a lot, man

Thank you for your work!

great video thanks! :)

Amazing explanation man !!

thank you so much for your sharing.

Is it possible to pass the function and the params to the worker file and return the result ? So it can be versatile..

Great explanation !

Great video thanks! that helped me to understand web workers for the first time. Could you please also make a video about promise, I still don't know if there is any background work going on with promises, or is await promise also being performed on the main thread, blocking it until the promise is finished?

Thank you!

Awesome man 👍

Great video! I would like to know why don’t you save the worker listener inside the onClick function

Thank you)

Thank you :)

Please do a video explain about service worker :) Great video by the way

but what happen if I tell the worker to do some heavy stuff before it has finished previous heavy stuff?

Very helpful, thnx

Awesome!!

i couldnt finish reading it but the first 2 sentences were inspirin LMAO

What the perfect explanation! Thank you for that! :) So technically said workers are calculated on a "virtual" threads of JS-engine, not on real CPU threads/cores?

nice explain

Super cool

how to use it in ReactJS project?

Solid example

Thanks!

can I use it in react?

Great video

Hi patrick, so web workers seems to be look like (async/await or promises) concept. eventually we defer specific task/s since it takes long time of response while in the same time we complete the other tasks so that we don't waste time in waiting. It is obvious that the main goal of these techniques is to control the outcome and performance of the application but I would like to see more details on the web workers and async/await concepts in real life example. Sync = Action A .. wait for the results of (A) Async = Action A .... wait for the results of (A) and keep doing other actions of (B), (C) and(D) This is how I understood Sync/Async/Web Workers .... Am I right ?

Hey man thanks for the tutorial. I am getting an error for Worker constructor when I use it like this. It is not defined for me. Also, if I use the new syntax where you put in url in the constructor like this: ``` new Worker(new URL('path'), import.meta.url) ``` I dont get any errors like this but in this case, when I specify the onmessage function in the worker script, self and onmessage are both undefined again. Any ideas?

Nice

Not readable on smartphones :'-(

Classic

Great. And please stop repeating that javaScript is "single threaded" JavaScript is not single threaded. This is only confusing new comers.

this is so helpful especially for a beginner

Great explanation!