New dissension in the Node.js community, driven by objections to the conduct of a Node.js technical committee member, have led to another fork of the JavaScript runtime engine.Ayo.js describes itself as  built on the Google Chrome V8 JavaScript engine.
It features an event-driven, non-blocking I/O model to make it lightweight and efficient.

That’s exactly how Node.js describes itself. A note on the Ayo,js GitHub repo even states a lot of the Ayo.js documentation still points at the Node.js repo.[ Getting to know Node? Don’t miss 10 JavaScript concepts every Node developer must master. | 7 keys to structuring your Node app. | Keep up with hot topics in programming with InfoWorld’s App Dev Report newsletter. ]
Two years ago, the IO.js fork resulted from a dispute over technical directions in Node.js (IO.js was later merged back into Node.js), but the new Ayo.js fork seems to be the result of community infighting more than any arguments over technology. Node.js technical steering committee member Rod Vagg, chief Node officer at Node.js provider NodeSource, raised ire over his tweet supporting a code of conduct article that Node.js community members described as inflammatory.

They also claimed he had interfered with the Node.js moderation process.To read this article in full or to leave a comment, please click here

Leave a Reply