All of these problems have acceptable, established, and time-tested solutions using Node.js itself, without the crippling caveat of lock-in to a new and unproven platform. And yes, despite the copy trying to distract from this fact, this is very much a case of lock-in, because built-in multithreading is not a Node thing. None of the mountain of Node code out there works on that expectation. Furthermore, JX seems to have its own proprietary packaging solution, SQL database, memory store, monitoring, and more. This isn't a point in its favor; it's just more lock-in.
These new features might be great and well-implemented, but if I'm going to benefit from them, I'm leaving Node.js behind and trusting that JX will be supported as well as Node itself is. I have no faith that will be the case. It's (perhaps unfortunately) and self-fulfilling prophecy: I doubt I'm alone in my thinking, and that feeds back into lack of a community coming together to support this fork.
My advice to the developers (who are clearly talented if they can put together something like this) is to refocus your energies on building stuff with (and on top of) Node.js instead of forking it.
Source: some hard-learned lessons