Echo JS 0.11.0

I was already sick and tired from process forking.. Wanna try this asap!!!!!

@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.

@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.

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 ?

Node.js supports c++ plugins. Unless you make it clear exactly why you needed a fork of it instead of a plugin, people will get confused. JavaScript is designed to be single threaded. The implementation may run async functions on other threads but programmers usually have no option to force spawn threads. If you need to spawn threads, write a native extension which does. I understand it may have taken a lot of work and I really appreciate the effort but we don't have any information about the real purpose of this (what can we do now that we previously couldn't?)

How is nodeJX different from Node.js? Other than many structural changes and small features, it supports multithreading, hence it is much more responsive and faster to run server side logic.

Haha. Right.

lolwut

Full disclosure: I'm a member of nodeJX team

Please see the blog posting below on some of the reasons behind developing multithreading capabilities: http://nodejx.com/why-node-js-multithreading-multi-context/ 

More to come this week including some internal benchmark results.

As promised, here is the results of our benchmarking study comparing the performance of NodeJX with Node.js and Vert.x

http://nodejx.com/nodejx-vs-vert-x-vs-node-js-cluster/

an alien !

Gents! Isn't it too early to say something? We needed this feature for our product development. It worked for us hence we thought it may work for others. Besides, Multithreading is not the only thing comes with nodeJX. We implemented other things and wanted to share with the public. We love node.JS! and want to do more with it. Thanks!

disc: I'm a nodeJX team member.

I think this is a bad idea. It defeats the purpose of Node.js imo.

The site, nodejx.com, does not work in Chrome 33.0.1750.22 dev :-(