Re:Napa.js: A multi-threaded JavaScript runtime
by stupidcar on Wednesday October 18, 2017 @09:10AM
(#15498820)
And if it isn't non-blocking? What if I'm writing a game and want to run parts of the rendering, AI, physics, etc. in parallel? Do I create a bunch of containers for each subsystem of my game and have them all communicate via IPC? This doesn't sound like a recipe for good memory/performance characteristics.
[ Parent
| on HN ]
Re:Napa.js: A multi-threaded JavaScript runtime
by stingraycharles on Wednesday October 18, 2017 @11:13AM
(#15499759)
But we’re talking about javascript here, a language that is async about almost everything.
I completely agree with what you’re saying for those other problems you describe. But for the typical node.js webapp, doing the one-container-per-core is perfectly fine.