It seems like node's big thing has been to argue for single-threaded
non-blocking everything as it's default.

Is the intent is to match node's semantics with Node.jar, such that code
would truly be portable between node.js and Node.jar?

In my case I've also used and liked RingoJS which does use threads and the
blocking CommonJS apis.

So partly I'm wondering if Node.jar will favor compatibility with node.js
over adopting a more Ringo-like approach to threads (or not).

Thanks,

Darren

Reply via email to