Comment by quaunaut
11 years ago
...Okay, normally I roll my eyes at people asking "What does this do" but Christ this is ridiculous.
From the FAQ:
> What is io.js?
> io.js is a JavaScript platform that is compatable with Node.js & npm.
What does that even mean?
Edit: Thanks for those answering. I started figuring out what it was, but sometimes folks really need to learn that "A correct definition" is not the same as "a useful definition". However, if it's as cool as described, definitely might give it a shot.
Edit2: Is this expected to be as stable as Node.js consistently? And how solid is the upgrade path- is it going to be a pain upgrading between versions the way Node used to be, or is there a smoother upgrade process? I guess what I'm wondering is, do I get any benefit from using this right now, or would it be smart to still wait for whatever version they consider release quality?
It's a fork of node.js with ES6 support. The goal is a faster release cycle and an updated V8 engine, plus an "open governance model" as opposed to Joyent's domination of node.js prime.
https://github.com/iojs/io.js
> It's a fork of node.js with ES6 support. The goal is a faster release cycle and an updated V8 engine, plus an "open governance model" as opposed to Joyent's domination of node.js prime.
For the record, I believe that's what should be written as the first answer on the FAQ (and maybe on the site's index.hml). The current one is atrocious.
For a comparison, node.js contributors are (http://nodejs.org/about/core-team/)
TJ Fontaine Alexis Campailla Fedor Indutny Trevor Norris Nathan Rajlich
Rather strange to see Fedor as a core team member in both projects, or at least one of them (likely node.js page) is out of date.
Its not strange, most of the people involved are core members of both projects. Its the same project, really. Its just that iojs actually has new releases, and node doesn't anymore.
Yes I know, I need to add `s/anymore/yet`. But the statement is pretty much accurate. Its been almost 2 years since 0.11.0 was released and 0.12 is nowhere in sight.
Are node/io permanently joined to V8? I know that Oracle has been putting some effort into getting Avatar.js to be fully compatible with node and run on the JVM, but it isn't gaining much traction.
I find Ben's inclusion on this list interesting, given his history with Joyent/the node community.
I felt like he got thrown under the bus with that whole uproar, and was glad to see him in there.
10 replies →
Even though he stopped being part of core, he has remained active in Node.js development. It's part of his job at StrongLoop I suppose. A fresh start with an open governance model at least should mean that most politics are set aside.
4 replies →
The fact that opinions like these are still a thing says more about the opinion than his commitment to the node/io/libuv community. edit: obvious commit statistics below/above.
What happened?
1 reply →
io.js is a fork/continuation of Node.js "unstable" 0.11.x branch. Node.js stable, under Joyent's stewardship, has been stuck in 0.10.x land for over a year.
io.js has many of the top core Node.js contributors. They're trying to move server-side JavaScript forward with open governance, faster release cycles, ES6, etc.
> io.js is a fork/continuation of Node.js
Thanks.
That website needs serious work in terms of wording. Absolutely zero information on the website apart from the extremely vague tagline. I clicked a few links and all I could find was politics. Without the context given on HN I would still be wondering:
Is it a node.js replacement? Is it a NPM replacement? Is it a dog? Is it a cat? Can I eat it?
Even you want to sell something to people (even if that something is free as in beer) they need to know what that something is, first.
completely agree. I didn't even get it was a node replacement. A spork of node? What is that? I might be missing some tech vocabulary, or just some native-english understanding. But the wording could be much more clear.
It will be interesting what Joyent will do with its 0.11 unstable branch and how popular io.js will get.
The merge between the current 0.10.35 branch and the 0.12 branch is almost done (https://github.com/joyent/node/milestones/0.11.15), we can expect version 0.11.15 within then next few days. 0.11.15 will be a release candidate for 0.12.
On the other hand, they've been saying that 0.12 will come out 'soon' for over a year, so this too may take longer than I expect.
1 reply →
Agree...couldn't find a clear explanation anywhere within several clicks of the home page. If it's a fork of node.js with ES6 support, as people are saying, they should put that on the front page or at the top of the FAQ section or on the front page of the documentation.
It's more than that: a lot of people who made node.js to what it is are now working on io.js.
It's more like a new version of node with a different name to circumvent trademark issues.
In a gist, io.js is node.js with faster release cycles using more up-to-date versions of V8 along with an open governance
link to gist?
Here I suppose: https://gist.github.com/maxogden/d96123138522c84cdb25
Nice.
io.js is a program that makes JavaScript run on a server.
io.js is a fork of node.js but is "better" because:
1) io.js always uses the latest JavaScript engine.
2) io.js is not controlled by private interests.
Really? I thought V8 makes JavaScript run on a server.
no, V8 makes javascript run, iojs makes javascript run on server.
2 replies →
V8 is just a JS engine, it is used in io.js, node.js, chrome, and chromium.
I still cannot figure out what this actually is besides Javascript
Google's v8 is the JavaScript. io.js provides APIs for performing disk and network io, using v8.
Node has IO methods as well...
It's basically a fork of nodejs
It's an implementation of the Reactor Pattern with some package management capability. Not a platform. Not a framework. Not an engine. Just a script.
You could literally say that about anything.
"Rails is just an implementation of the MVC pattern, not a framework."