>>19Like I said, the ideal would be to have both non-blocking and threading. Node's non-blocking engine is the best there is, ever, and there is no way to do non-blocking without callbacks (maybe you could sugar it to hide the lambdas, though). A for loop is actually sugar for a callback, if you consider callback a instruction that is stored instead of executed immediately. So there you have it, there wouldn't be programming as we know it without callbacks, we'd all be programming in assembly. It can't be that it is only event callbacks that you don't like, because even haskell has events, and any language with events will have a event callback for each of them. Some of these languages use threads to schedule the events, node doesn't need to, but that doesn't change much in the syntax.
TLDR: if you're doing events without "callbacks" it is just some sugar, and if you complain that node doesn't have threads, you can always spawn many node processes and have them communicate.