Live data from Hacker News

Io.js 1.0.0

iojs.org

111–120 of 190 posts

Re: Io.js 1.0.0

#111

...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,…

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.

Re: Io.js 1.0.0

#113
post #103

Earlier quoted context omitted.

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.

Re: Io.js 1.0.0

#114
post #18

...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,…

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.

Re: Io.js 1.0.0

#115
post #91

Earlier quoted context omitted.

The huge collection of modules on npm is one of the strongest factors node.js has going for it, so it makes sense for them to emphasize that they're not breaking compatibility with this in forking node.

Yes, but something "JavaScript runtime with npm compatibility" would be friendlier and significantly easier for people to understand.

They don't provide the Javascript runtime - Google does that. This is a fork of Node.js - glossing over this is at least a little disrespectful to Node.js.

Re: Io.js 1.0.0

#116
post #18

Earlier quoted context omitted.

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 s…

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.

Re: Io.js 1.0.0

#117
Am I alone in being bemused and amused by this:

  Version 1.0.1 (Beta stability)
Surely the main point of a 1.0 release is "stability" and to no longer be "beta"?

Re: Io.js 1.0.0

#119

Earlier quoted context omitted.

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 Current Project Team Members ============================ Isaac Z. Schlueter Ben Noordhuis Bert Belder Fedor Indutny Trevor Norris Chris Dickinson Colin Ihrig Mikeal Rogers Rod Vagg

I find Ben's inclusion on this list interesting, given his history with Joyent/the node community.

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.

Re: Io.js 1.0.0

#120

...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,…

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 Current Project Team Members ============================ Isaac Z. Schlueter Ben Noordhuis Bert Belder Fedor Indutny Trevor Norris Chris Dickinson Colin Ihrig Mikeal Rogers Rod Vagg

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

Post reply on HN