Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

My first week.. Seriously, why a foundation needed ? #30

Open
jayolsen opened this issue Feb 26, 2015 · 0 comments
Open

My first week.. Seriously, why a foundation needed ? #30

jayolsen opened this issue Feb 26, 2015 · 0 comments

Comments

@jayolsen
Copy link

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 ;

  • 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant