> The biggest selling point of Node folks has been the "single threaded, event driven" model, right? No, it's "JS on the server." > it's impossible to wait or

> The biggest selling point of Node folks has been the "single threaded, event driven" model, right? No, it's "JS on the server." > it's impossible to wait or block an I/O request while at the same time also letting the other part of the code engage in other tasks No, it's absolutely possible. You can ask the network stack, "do you have any new packets" and the stack can say "no" and you can go off and do work before coming back to ask "do you have any new packets" and the network stack says "yes" before your (still single-threaded) application reads those packets and does something with them. Concurrency is not parallelism.