they all read from wikipedia except this one , this video is truly a masterpiece and i love it

Thank you very much Sayed Dileri! Glad you’ve learned valuable things here! I’ll try my best so that you can learn even more in future contents! Thanks again!

Yeah I understand that first feeling you're talking about! Fortunately after a while and learning these core concepts it won't be like that anymore! Glad you found this useful and thanks for your comment!

That's because the most of people have learning lazy of right way, because that is the harder way, but also the more efficiently way.

Thanks Gabriel!

'_"

Thanks Yahya for your kind words! Next up we'll learn about these core concepts in node: EventEmitters, File System, Streams, Net, and HTTP. Once we learn about them, we will have enough knowledge to build some intricate projects, so the course is going to get project-based after that (we'll build a very complex application and learn about so many new things along the way). And of course, once we complete our application, we’re going to learn about deployment, scaling, monitoring, security and so much more! Thanks again for your interest in the channel Yahya!

Welcome @@Cododev.Thanks for replying! I am waiting and really excited about that path. ☺☺🤗

Thanks Vahan! Appreciate it!

That’s a great question! Well to start, async programming is totally different from multi-threading programming. And about the network requests, yes libuv doesn’t open a new thread to handle each request, rather the operating system will somewhat somehow get the requests and handles them USING ITS OWN THREAD(S). So technically there are multiple threads involved but those OS threads have nothing to do with our threads, in other words, we don’t need to care about them in our code, so we are doing all these in only one thread, and we are also doing these asynchronously. This outsourcing you mentioned is the case, if you can send me a link to these articles, I will take a look and let you know with more details. Thanks!

@@Cododev You are completely right , i did some digging few days ago and turns out most of I/O operations are non blocking and the device driver is actually responsible for completing the task . Internally, OS uses I/O Request Packets(IRP, think of it as an object which carries the state of the task and the metadata) to send to the device driver which changes the status of the IRP (lets say we are writing to a file , it will set the status to pending and give the control back) and as soon as the I/O is done , an interrupt signal is sent to continue the execution of the code which was written after await (and here the event loop is beneficial as the callback that is pushed into the stack gets executed only when the call stack is empty so we get the kind of execution that we see in node). There are languages like c# which actually does more/different optimisation on the compiler level (like breaking the code which has async operation into 2 parts , 1st is just before the async operation and the other is after the async and when it receives the interrupt signal , the code after the async operation starts executing) blog.stephencleary.com/2013/11/there-is-no-thread.html

Thanks a lot for your support Shishir!