Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Io.js 1.0.0

iojs.org

Post reply on HN
Print view View original

41–50 of 190 posts

Re: Io.js 1.0.0

#41

Post by pcl »

tach4n wrote: post #22
aasarava wrote: post #8

Tip 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: http…

If I were them, I'd say something like:

"io.js is an api-compatible alternative to the node.js runtime, including support for the npm ecosystem, that aims to release faster than the node.js release cycle and move according to a community-driven open governance model."

Given the tremendous volume of packages released to npm, the current one-liner initially just doesn't convey much information. In context of the comments here, it all parses perfectly, but I was one of many who needed this context to understand the (apparent) goals of the project.

Re: Io.js 1.0.0

#42

Post by _greim_ »

I suspect there will be a split in the npm ecosystem now, not so much along node/iojs lines but along es5/es6 lines. There's already been lots of discussion about whether module builders should publish es6 code, or should everything be transpiled down to es5 code in order to keep the ecosystem unified (the unspoken caveat being, around es5).

I think es5 is a dinosaur as of today, so I say go ahead and publish es6 code, and if you want to be nice to es5 people then add a prepublish transpiler that makes something like this possible:

    // es6 people can do
    var foo = require('foo');

    // es5 people can do
    var foo = require('foo/es5');

Re: Io.js 1.0.0

#44

Post by k__ »

dsissitka wrote: post #6

Version 1.0.0 (Beta stability) The hell? Seems it's intentional: https://github.com/iojs/io.js/issues/251#issuecomment-694177...

Doesn't 1.0.0 simply mean, API stability?

Re: Io.js 1.0.0

#45

Post by tlrobinson »

silverwind wrote: post #35
scope wrote: post #23

how would one go about deploying (say on Heroku) an iojs app?

Heroku has pretty good node support, but I'd doubt they support replacing the binary yet, so you'd have to wait for Heroku to support that. For manual deployment, the single iojs binary and your project folder should suffice, along with a way to start/restart your app automatically.

Heroku supports arbitrary "buildpacks", it should be easy to create one for iojs.

Re: Io.js 1.0.0

#46

Post by _almosnow »

From their changelog, it seems that addons changed, does anyone know if current npm packages will still be usable?

Also, good to see bnoorhuids in there.

Re: Io.js 1.0.0

#47

Post by dan15 »

tach4n wrote: post #22
aasarava wrote: post #8

Tip 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: http…

We should start referring to PHP as a "Composer compatible platform" and Python as a "PyPI compatible platform"

Re: Io.js 1.0.0

#48

Post by adregan »

acdanger wrote: post #21

"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?

Homebrew asked me to overwrite my node symlink with the iojs symlink. I decided to link iojs to iojs on my own. I hope I'm not spinning myself into some technical debt here, but for now, I'd like to maintain both.

Re: Io.js 1.0.0

#50

Post by throwaway432324 »

nevi-me wrote: post #40
silversupreme wrote: post #27

Earlier quoted context omitted.

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

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.

I hope so. Pretty much everyone on that list except isaac and mikeal are apolitical.

Mikeal is overtly political. Isaac is political from time to time since he's strongly aligned with the identity politics mob that attacked ben noordhuis back in the day. I really hope identity politics doesn't creep into the io.js governance.

Post reply on HN