Node.js Tutorials - 43 - Microtask Queues 

Don't know what you have to apologize for. The switches between the diagram and the code are fantastic and help more. Thank you

The first time I saw the diagram, I skipped the entire tutorial, but after a few months, I started watching it again. The phase and queues in Node JS are now clear to me... thank you so much!

Your explanation is the clearest one I've ever heard. Thanks a lot!

Your teaching style is so so beautiful that I was able to predict the result. Thank you so much :)

You are one of the best teachers I ever met, sir. Everything explained well and short to the point. Got it in one go and I got my confidence boosted!

Core concepts explained with a heart winning simplicity.

I magically got it right on the first try thanks to your great explanations.

Sir! You are great in this field!

Your teaching style is so so awesome. I'm able to predict the result. Thank you :)😀

Really great explanation and on point with visual representation 👍

Thanks a lot. You have made my day!

Simply outstanding🔥. U made it easy to catch those complex concepts 🎉

Thank you so much for this tutorial. It helped me a lot

your explanation is soooooo good that I got it right

It's been wonderful sir, and i got it right in the first try and you made it possible for me to guess

Greate explanation with patience👌👌

I always give your video a like before even watching it.

great job! thank you

Thanks a lot, Vishwas

Just wow concept 🙏🥰

Awesome Video...

Well explanation

Got right man!

Yes i got the same results

11:57 I thought the nested nextTick ("nextTick inside nextTick") will be executed in the next event loop iteration.

thanks teacher 43

Hi, your explanation is the clearest one I've ever heard. Thank you very much, but can I ask you for this slide for reference?

Got it right

How does call stack knows to which queue it should put callbacks to ???

Hello sir.. i got the promise.resolve.then consoled first before the process.nexttick console

Got right for next tick, but little different for promise.resolve,

Also, I noticed that using Promises puts the execution of the handler to the next cycle. While using regular js callbacks execute right away in for example IO or Timer cycles. Is it fair to say that using callbacks is faster than using Promises? using Promise will add an additional cycle event if it is just Promise.resolve?

i got that right

According to my understanding, the global function will also be removed from the call stack before running any async code

The nextTick queue takes precedence over the microtask queue, but the example in (5:50 to 8:35) is only half correct. In fact, if someone runs it as an ESM script (.mjs file or with type="module" in package.json), the output will always be: 2 -> 3 -> 1 That's because instead of executing it synchronously, node schedules it as a microtask callback (like wrapping everything in queueMicroTask(() => { ... }), kind of). So after executing the code, the event loop grabs the next callback in the microtask queue until it becomes empty before checking the nextTick queue. Same thing for the 2nd example. Output for ESM would be: promise 1 promise 2 promise 3 nextTick 1 nextTick 2 nextTick 3 nextTick inside Promise nextTick inside nextTick

Hey, I have a question. Why did you repeatedly use the phrase 'user-written synchronous code' in your explanations? Why do we have to mention 'user written'?

I am a bit confused. I thought the inner CallBacks would join the next iteration. which would mean the sequence would be NextTick1, NextTick2, NextTick3, PromiseResolve1 PromiseResolve2 PromiseResolve3 NextTick inside NextTick, Promise inside Promise

*space bar* 4:06 ~ "That's what she said". *space bar*

Promise.resolve().then(() => console.log('start resolved promise')); process.nextTick(() => console.log('start nextTick')); I have run this in my local but bit confusing for me. I am getting [nodemon] restarting due to changes... [nodemon] starting `node justDemo.js` start resolved promise start nextTick [nodemon] clean exit - waiting for changes before restart As you can see I got in same order, not able to understand.

So Calling nextTick inside nextTick actually executes the callback in the same cycle and not in the next.

In my case promise queue running before process.nextTick queue

🙏👍👍

Why did they make it so complex? Why do we need so many queues?

sir where is your feet i want touch it for it's clear explaination.............thanks sir.........always respect for great teacher.......

{2024-01-30}

Good tutorial but, god, your ending of all senteces is so annoying

Promise.resolve().then(() => console.log("this is Promise 1")); process.nextTick(() => console.log("nextTick 1")); Why output is actually coming : this is Promise 1 nextTick 1