Echo JS 0.11.0

<~>
pokani 3746 days ago. link 4 points ▲ ▼
@egecan: on current node.js design you can't run the 'node.js' code in a separate context! although there are solutions, they are limited to compiling JS on v8 (webworker).. Since the design is not supporting that (lots of static variables in original code! and much more..) you can't do it by developing addin etc.. 

Simply, implementing multithread capabilities 'properly' into node is a big structural change and requires a fork.

Replies

egecan 3741 days ago. link 1 point ▲ ▼
@pokani I'm simply pointing to the fact that the whole node ecosystem is built by assuming that node is single-threaded. When multiple threads are necessary, most people write it as a native extension and provide a callback to the JS world. I'm not discouraging you or anything. I love innovation. I just want to understand how this helps me. I see, that one may start pushing blocking operations to other threads, but doesn't it make sense to do such operations on a lower level anyway? I also think that this fork is too tied to a web framework.
pokani 3740 days ago. link 1 point ▲ ▼
as far as I saw from the documentation, you can even run your existing node.js app as a separate thread. And there is no lock etc. thing since there is no context sharing.. I would prefer multiple threads and instances of my solution + multiple processes. instead single process + single thread. In other words, how about clustering both internally and externally ?