Everything is async in node, because doing sync operations in event loop is terribly slow.
People have tried to retcon node's choices as being based on some sort of deep technical justification, but that's not the case: its limits are the limits of the material it's made of, not a specific design choice.
If you look at more advanced VMs like the CLR or JVM then they support all modes of operation: synchronous/blocking (which is often what you want), synchronous/blocking with many threads, async with callbacks, async with continuations ... node only supports one. How is that better?
Look at this page and tell me the JVM is better: https://docs.oracle.com/javase/7/docs/api/java/util/concurre...
The page you linked to shows a full and complete library of concurrency tools, which you don't have to use if you don't want to. How is this evidence of being worse?
Oh, and your link actually DOES show that the JVM is better. It can give you everything node.js has and then some.
If you want to see something like node.js for grown-ups, take a look at Vert.x or Akka (& Frameworks based on it), for example.
(Sorry for the snark, it's been a long day...)