napajs

Each thread or worker is a V8 Isolate, each with their own GC. I don't think WeakMaps could cross the isolate boundary. The project lists a set of "transportable" types, which can be passed in as an argument when calling a worker function - https://github.com/microsoft/napajs/blob/master/docs/api/tra...

In https://github.com/microsoft/napajs/blob/master/docs/api/tra... it sounds like there aren't completely isolated runtimes - "JavaScript standard built-in objects in the whitelist can be transported among napa workers transparently" and it seems to imply they are not transported via serialization but via a sharing mechanism leveraging multiple threads in the same runtime. (And also it talks about implementing your own Transportable classes)

I’m curious to know if they ever looked at https://github.com/Microsoft/napajs from Microsoft or any other in-nodejs solutions to deal with the need for multithreading vs launching multiple processes...

Microsoft's Bing group customized Node.js for CPU-bound tasks: https://github.com/Microsoft/napajs/wiki/Why-Napa.js Napa.js: A multi-threaded JavaScript runtime https://news.ycombinator.com/item?id=15498219 (Nov 2017) Their deal-breaker against using node-cluster was a need to use shared memory for IPC.

Take a look at microsoft's napajs: https://github.com/Microsoft/napajs

There is a roadmap on GitHub https://github.com/Microsoft/napajs/wiki/roadmap

In case anyone missed it, a Node module used in production at Bing to multi-thread shared memory for CPU-intensive work hit the big time last week. https://github.com/Microsoft/napajs/wiki/Why-Napa.js a bit edited: 1) quick iteration 2) multiple cores 3) share memory with structures 4) fine granularity parallelism, minimizing communication cost Discussion: https://news.ycombinator.com/item?id=15498219 (Oct 2017, 201 comments)

I know it's addicting to be dismissive, but: https://github.com/Microsoft/napajs/wiki/Why-Napa.js

A key design goal is to make all workers within a zone symmetric, broadcasting/executing to specific workers is an anti-pattern. Please see: https://github.com/Microsoft/napajs/wiki/introduction#zone

My personal theory is that they're trying to improve the JS engine in Electron so they can improve VSCode. The VSCode people have posted some performance complaints in the past. I would assume this would benefit desktop JS most, so it'd undoubtedly help Electron apps. EDIT : There's a better explanation at https://github.com/Microsoft/napajs/wiki/Why-Napa.js

Here is why napajs is started: https://github.com/Microsoft/napajs/wiki/Why-Napa.js

Have you read the docs? Just go read this https://github.com/Microsoft/napajs/blob/master/docs/api/mem... and tell me you don't feel uncomfortable. This is the kind of baggage you are bound to get with such solutions and once you end up writing a steaming pile of code, then you need a thread safe logging and debugging story.

Wait what? Why are they getting rid of simplicity and model that just works. Once again Microsoft managed to put on some C# programmers on JS. The first thing they thought was why doesn’t it support threads! Let’s build thread support and get a promotion! Edit: I would question usage of Node if everything you are doing is CPU bound. I think people started down-voting me without going through docs, I mean just read this documentation page and tell me this is right https://github.com/Microsoft/napajs/blob/master/docs/api/mem...