Understanding Asynchronous JavaScript

Understanding asynchronous JavaScript is an important concept. This concept leads to a better understanding of callbacks and promises.

For more resources on JavaScript:

Full personalized courses on JavaScript:
Courses offered on Udemy: Getting Started or Advanced Topics at a huge discount:

Tutorials referred to in this video:

[prabhakaranjeyamohan]

Amazing pace, clear voice, solid knowledge, mature and patient teaching. Sir, you are an awesome teacher.

[jude]

Sir, you are a good instructor glad I found this video. Thank you!

[ivangutowski-smith]

he he, I watched one video, then each one keeps referencing other videos I should watch first. The rabbit hole goes so deep ha ha - thanks for linking the relevant mentioned videos

[mubasshirahmed]

Sir, your explanation is very lucid. I can't thank you enough.

[muslimman]

The best Asynchronous example I ever heard. Thank you, sir

[tslqs]

Hello, can you please tell me what editor and what theme do you use?

[noumanmalik]

Thank you, it really helped me revising the concept.

[magdaw]

Thank you! Nobody explains JavaScript better than you! Is there a "async await" video? I wonder if i missed that somewhere.

[rao]

This is a very simplistic explanation. The execution of JavaScript is always synchronous from a call stack. What setTimeout does is delay the moment that a callback is pushed into the stack. And it will push into the stack after X milliseconds which means that it will actually be executed after all the stack is done executing. So it may not even be executed after X milliseconds. If this happens on a browser, other tasks may be executed before the callback like Dom rendering for example.

[denniskamonde]

Thank you sir ....am glad you'll do promises next

[haciendadad]

Could have been an opportunity to introduce the Event Loop topic and Blocking Threads vs non-blocking threads.

[yamatube]

one of your videos is numbered 97 but i cant find the playlist for it.

[simplified_af]

it's not really the callbacks that makes it asynchronous but its the web APIs like settimeout which makes it asynchronous. its not like you create your own callback and it's magically asynchronous because javascript is songle threaded. the web APIs which aren't coming with the javasript runtime engine but with the browser is what makes thr ehole thing asynchronous

[mimishiba]

Play at 1.25x speed. It sounds like you're purposely talking slower than necessary to lengthen the video duration

[petersingh]

This is just a plug. Which I have to say, the guy has 20+ yrs of JS experince and his 'courses' are as weak as yesterdays unfinished can of beer. better of elsewhere if you want to understand callbacks, async