My comment was specifically about module isolation and message-passing, the design patterns, not language implementation, preemptive vs cooperative or whatever.
I hate to harp on this, since you were downvoted to oblivion, but node.js doesn't have module isolation, as a crash in one function will stop the entire program.
And it doesn't have message-passing since it doesn't have multiple processes. There's nothing to pass messages to.
The only design pattern it shares is splitting code into subsets, and every language (that matters) has that.
On node.js: not if you use domains (0.8+) to isolate module exceptions, and you do (should) have multiple processes. On the client, a module throwing an error won't crash the browser either. Finally, events are a form of message-passing.
