Echo JS 0.11.0

<~>
egecan 3990 days ago. link parent 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.

Replies

pokani 3990 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 ?