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

51–60 of 190 posts

Re: Io.js 1.0.0

#51

Post by davesque »

quaunaut wrote: post #10

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

Re: Io.js 1.0.0

#53

Post by thomasfoster96 »

From what I can understand, io.js is now node with the latest version of v8 and ES6(+ES7) features enabled by default (as opposed to behind a flag).

I'm wondering, what technical reasons are there for Node not using the latest version of v8 for each release? I can understand Node keeping some new ES6/7 features behind a flag (just as some are behind a flag in Chrome).

Re: Io.js 1.0.0

#54

Post by btown »

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's way ahead of you... https://github.com/heroku/heroku-buildpack-nodejs/blob/a77cd...

EDIT: To clarify, though I haven't tried it myself, it looks like you can just specify `"engine.iojs": "1.0.0"` in your package.json, and Heroku will install the entire io.js system for you.

Re: Io.js 1.0.0

#55

Post by ivank »

thomasfoster96 wrote: post #53

From what I can understand, io.js is now node with the latest version of v8 and ES6(+ES7) features enabled by default (as opposed to behind a flag). I'm wondering, what technical reasons are there for Node not using the latest version of v8 for each release? I can understand Node keeping some new ES6/7 features behind a flag (just as some are behind a flag in Chrome).

V8 updates bring incompatible changes to the V8 API, and many node extensions written in C++ need to be updated. Hence the decision to stick with an old V8, even though it's no longer maintained by Google.

There is a compatibility layer to assist with making these modules work across different V8 versions: https://github.com/rvagg/nan

Re: Io.js 1.0.0

#56

Post by wycats »

_greim_ wrote: post #42

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

Important to note: because JavaScript itself is always backwards-compatible (1JS), any code that runs on Node will run on iojs, but not necessarily vice versa.

That means there need not be a split in the ecosystem: people who want maximal coverage can target ES5, while people who want the latest features can target ES6. Unlike the browser, however, where people can't control their runtimes, I suspect there will be much less tolerance for sticking with older versions of JavaScript.

Indeed, the pain and suffering people have felt with IE6 will likely make everyone much more willing to reject an unnecessary lowest-common-denominator approach on the server. We're liberated on the server. Let's act like it.

Re: Io.js 1.0.0

#57

Post by btown »

shadowmint wrote: post #29
untog wrote: post #12

As 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 )

> "npm" does not stand for Node Package Manager. It is officially an abbreviation for “npm is not an acronym”. We do enjoy novel pun-making though.

I couldn't resist: https://github.com/npm/npm-expansions/pull/245/files

Re: Io.js 1.0.0

#58

Post by mintplant »

dan15 wrote: post #47
tach4n wrote: post #22

Earlier quoted context omitted.

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"

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.

Re: Io.js 1.0.0

#60

Post by j_0 »

btown wrote: post #54
silverwind wrote: post #35

Earlier quoted context omitted.

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's way ahead of you... https://github.com/heroku/heroku-buildpack-nodejs/blob/a77cd... EDIT: To clarify, though I haven't tried it myself, it looks like you can just specify `"engine.iojs": "1.0.0"` in your package.json, and Heroku will install the entire io.js system for you.

Came across this just before opening this thread, you are correct https://twitter.com/hunterloftis/status/555234067520565249
Post reply on HN