"This package will install io.js v1.0.0 and npm v2.1.18 into /usr/local/. The binary /usr/local/bin/iojs will also be symlinked as /usr/local/bin/node."
Why the symlinking as node?
Io.js 1.0.0
21–30 of 190 posts
Re: Io.js 1.0.0
#22Tip to anyone rolling out a library and wanting others to start using it: It'd be helpful if the home page or the FAQ explained what io.js actually does and why a developer might want to explore it further. "Bringing ES6" is only helpful if you know what ES6 is and have already decided it's something you need. Likewise, the FAQ simply says io.js is compatible with Node.js and npm, but that doesn't give you much to wo…
You're right that the page linked in OP needs improvement. The phrase to focus on is this:
> io.js is an npm compatible platform originally based on node.js
It's not a library, it's a platform that's based on node.js. It's more or less a fork of node or "spork" as they call it.
The github repo is a bit more clear: https://github.com/iojs/io.js
The main point seems to be that it's run on an open governance model: https://github.com/iojs/io.js/blob/v1.x/GOVERNANCE.md
Re: Io.js 1.0.0
#23how would one go about deploying (say on Heroku) an iojs app?
Re: Io.js 1.0.0
#24"This package will install io.js v1.0.0 and npm v2.1.18 into /usr/local/. The binary /usr/local/bin/iojs will also be symlinked as /usr/local/bin/node." Why the symlinking as node?
Because Io.js is a Node.js replacement, but most of the time you're probably going to instinctively type `node script.js` and not `iojs script.js` so the symlink is just a helper.
Re: Io.js 1.0.0
#25I have no issue with this fork but why oh why did they drop semantic versioning ? Do they want us to waste our time reading every single changelog ?
Re: Io.js 1.0.0
#26OP: sorry to nitpick, but the proper capitalization is 'io.js'.
HN auto-capitalizes the first letter when submitting, sadly. EDIT: Turns out it doesn't do it a second time if I edit, so, fixed :) EDIT2: Aaaand it reverted itself to Io.js, somehow.
Re: Io.js 1.0.0
#27...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
I find Ben's inclusion on this list interesting, given his history with Joyent/the node community.
Re: Io.js 1.0.0
#28"This package will install io.js v1.0.0 and npm v2.1.18 into /usr/local/. The binary /usr/local/bin/iojs will also be symlinked as /usr/local/bin/node." Why the symlinking as node?
Because Io.js is a Node.js replacement, but most of the time you're probably going to instinctively type `node script.js` and not `iojs script.js` so the symlink is just a helper.
It's for bin scripts such as NPM which refer to the executable directly. See here: https://github.com/iojs/io.js/issues/249
Re: Io.js 1.0.0
#29As someone who tries as hard as they can to avoid project politics and the like: is this the new Node.js? By which I mean I know it isn't the Node project, but where is most of the mindshare these days? Is io.js a small offshoot or has it taken most of the Node devs with it? Or is it the same code just with a more aggressive release schedule? Also, when do we go back to one executable already?
If we're lucky this will turn into the 'unstable branch' with new features and things which is periodically folded back into the 'stable' node.js platform.
...but if node wont play ball, it'll become 'the new node', yes.
(there's a lot of backstory to this, which you can read about here: http://blog.izs.me/post/104685388058/io-js)
Re: Io.js 1.0.0
#30I have no issue with this fork but why oh why did they drop semantic versioning ? Do they want us to waste our time reading every single changelog ?
They didn't drop semantic versioning (assuming you're talking about http://semver.org/), they're switching to it (see https://github.com/iojs/io.js/issues/28).
Node.js uses MINOR even = stable, odd = unstable (which is not semver) and is still in 0.x even though it's been used by giants in production all over the world for a couple years.