I spent a whole week playing with io.js, nodejs. Several years of objective-c programming experience, I couldn't see a mentionable difference between io.js and node.js. Maybe because I'm new to node. For an inexperienced node developer, node.js offers a smoother experience (npm).
How 'npm' fails supporting io.js is an unsolved puzzle indeed. Anyway;
Here goes the question that I'm lost. io.js is around because of ;
an unwanted corporate mentality behind node.js
struggling node.js start-ups (node.js copyright)
If it was the first reason only, why to deliver it back to another corporate ? I don't know if a corporate sponsored foundation has any place for an open governance. I do agree with @eranhammer
If this was the plan right from the beginning (now npm problem makes sense), then there is nothing to discuss though. But I'm pretty sure this is not the case?
I'm wondering what (magnificent) io.js people would say about these stuff.
Seems this is the right place for a none or semi-technical discussion.
See also; @eranhammer 's why-i-do-not-support-a-node-foundation
I spent a whole week playing with io.js, nodejs. Several years of objective-c programming experience, I couldn't see a mentionable difference between io.js and node.js. Maybe because I'm new to node. For an inexperienced node developer, node.js offers a smoother experience (npm).
How 'npm' fails supporting io.js is an unsolved puzzle indeed. Anyway;
Here goes the question that I'm lost. io.js is around because of ;
If it was the first reason only, why to deliver it back to another corporate ? I don't know if a corporate sponsored foundation has any place for an open governance. I do agree with @eranhammer
If this was the plan right from the beginning (now npm problem makes sense), then there is nothing to discuss though. But I'm pretty sure this is not the case?
I'm wondering what (magnificent) io.js people would say about these stuff.