> Node's threading model is process based message passing. So when you say node based multithreading what you're actually saying is spinning up a worker process

> Node's threading model is process based message passing. So when you say node based multithreading what you're actually saying is spinning up a worker process to pass a message to. Yep, which is a perfect solution to the problem of scalability. > Then you have the nightmare of trying to get people to think in event loops, because node (fundamentally) turns any backend task into a browser execution model pretending to be a backend function. We're a team of professional Javascript developers on the frontend; we know the event loop and task queue semantics very well :) > I'm not saying it's the wrong thing for your use case, but I can totally relate to why management/programmers from other paradigms have so much damn trouble wrapping tgeir head around JS. Fair enough, but like... am I crazy to think that the proper managerial response to "I don't understand this" should be "maybe I should ask the experts I employ" instead of "so no one gets to use it ever"?