Hacker News Reader

This looks a lot like web workers, which Node.js does not have. Hopefully they will add it. https://github.com/nodejs/worker/issues/2

View on HN

fork works fine in node.js

why down vote ? fork is fine as long as the communication between the two processes is low-bandwidth.

It works fine for many use cases but has serialization overhead.

Shared memory & low overhead sharing of expensive objects is probably the primary reason to use Napa

I don't think Napa features shared memory though, does it?

Since everything is in a single process, they can be shared via native structures. Each JS thread has its own heap, there will be a cost to transfer the shared native structures into JS object.

For complex objects, usually JSON is used thus marshall/unmarshall is needed. But for objects like UTF-8 string or ArrayBuffer, the same layout is used across JS and C++, thus at almost no cost.

Another thing is that between addon-modules, they can pass pointer of native structures (like Buffer) using 2 uint32 through JS. In this case, JS works as a binding language.

Reply on news.ycombinator.com