This is an interesting point of view. I personally find the erlang approach -no shared memory- to be the least error prone, and as a consequence the most effici

This is an interesting point of view. I personally find the erlang approach -no shared memory- to be the least error prone, and as a consequence the most efficient for developers. With Erlang you can't share memory [0], but in exchange you get sequential code (no callbacks or yields), true parallelism, and even distribution over a cluster. With node.js all the asynchronous calls live in the same memory space, but code is written with nested callbacks (or yields), and of course you get no parallelism. [0] There are shared dictionaries for when it is really absolutely necessary.