I think the author you are referring to adds more confusion than clarity (the guy says he is just learning node, so you really ask for a blind, leading-blind situation in using this to learn), I donβt know why does he think that Node claims to be "this" (i.e. Node.js) is single-threaded. I have never seen this. The fact is that inside Node, your code is all executed in one thread, which means that the developer is freed from talking with different disagreements. (Many consider this a key advantage, but I think it can be argued that you are simply trading one type of template (for semaphores, etc.) For another: handling asynchrony (although there are several approaches to reduce the more tedious aspects of this).
Although I'm not quite sure what you are asking, I think if you watch this video ( https://www.youtube.com/watch?v=L0pjVcIsU6A ) between 3 minutes and 7 minute marks, you will have a moment "o , I get". The visual presentation that the presenter uses (which, it seems to me, he takes from the preso by the original creator of Node) is much easier to understand than a wall of text that would describe the same thing using only words.
Hope this helps.
source share