{"id":298,"date":"2017-07-24T12:57:32","date_gmt":"2017-07-24T12:57:32","guid":{"rendered":"http:\/\/www.concettolabs.com\/blog\/?p=298"},"modified":"2025-04-15T09:17:17","modified_gmt":"2025-04-15T09:17:17","slug":"node-js-vs-io-js-mimes-better","status":"publish","type":"post","link":"https:\/\/www.concettolabs.com\/blog\/node-js-vs-io-js-mimes-better\/","title":{"rendered":"Node.js vs io.js: Who Mimes Better?"},"content":{"rendered":"

Node.js vs io.js | Although there is no clear winner among the two, each of them stands out in their way to impress its prospects. So let\u2019s study them in detail on a comparative note, so as to give you a clear picture of which one suits you best.<\/p>\n

<\/span>Node.js has been forked! The big tech world news.<\/span><\/h2>\n

But was it that big, when Node has already been forked in the past? \u00a0Remember JXcore. And this time, four of the top contributors of Node.js<\/strong><\/a> are part of this forked activity. The main reason behind this forked project io.js was the fact that the number of commits on node.js over the past few years had measured a declining trend.<\/p>\n

\"Node.js<\/p>\n

And also one of the other prime reasons was dissatisfaction in the way the project was being handled by Joyent. Efforts were made by some of the core contributors to provide a proper structure to Node and solve the problems related to it, to some extent, but in vain. In the name of \u2018Node Forward\u2019 independent efforts were made to improve the Node ecosystem, but that too was a failure.<\/p>\n

So finally Fedor Indutny, one of the prime team members, came up with the fork named io.js. Others followed the league.<\/p>\n

<\/span>Here is all you need to know about io.js<\/span><\/h2>\n