Or you use promises/observables (with arrow functions) or generators or async functions, and they don't. 2014 called, they want their node problems back. Basic

Or you use promises/observables (with arrow functions) or generators or async functions, and they don't. 2014 called, they want their node problems back. Basically almost none of the criticism in this whole thread is true today. The only remaining true bit is that node still relies on cooperative multitasking and one of the tasks can hog the CPU of a single worker. Which isn't very good, but still, way better than say, the good old Rails 1 request per process model. Someone should probably do a proper benchmark to show how different numbers of workers at different CPU workloads affect a node service's response time / latency. Especially with multiple processes (cluster), I would bet the effect would be much better than what people expect it to be.