[wakeywakeywakey]

Having reviewed the relevant tweets/GitHub issues/blog posts, I feel most of the noise is generated by people who make it their mission to find things about which to be outraged.

The NodeJS brand has the momentum necessary to build great things. If they squander it by cry-wolf-forking every time there is an internal disagreement, another JS engine (e.g. Chakra) will take the helm.

[AlexeyBrin]

> The NodeJS brand has the momentum necessary to build great things. If they squander it by cry-wolf-forking every time there is an internal disagreement, another JS engine (e.g. Chakra) will take the helm.

Node.js is not an engine, Node.js uses the V8 engine (same engine that powers the Chrome browser). Technically you could use Node.js with the Chakra engine or other JavaScript engines.

[wakeywakeywakey]

Right, I could have phrased it differently: another brand/community/project/environment/solution, like Chakra, will take the helm.

The greater point I was making is that this fork seems to be a baby-and-bathwater reaction; disagreeing with one member's behavior does not make the entire community toxic.

[flanbiscuit]

Didn't Microsoft do that? Created a version of Node using Chakra as proof of concept

[BinaryIdiot]

No, Microsoft modified node to allow drop in replacement of the JavaScript engine and then provided a Chakra backed version of node. It actually seemed to work pretty well and was pretty well received by the community. I believe others were attempting to do the same with the Firefox JS engine (SpiderMonkey? I can't remember what it's called) using the same base of work Microsoft created.

[askmike]

> I believe others were attempting to do the same with the Firefox JS engine (SpiderMonkey? I can't remember what it's called)

You don't mean Rhino? That was years ago when node was just gaining traction.

[yellowapple]

My impression is that Rhino was a separate project entirely.

[KGIII]

It seems to me that when one seeks umbrage, one finds it.