Earlier quoted context omitted.
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
Io.js 1.0.0
71–80 of 190 posts
Re: Io.js 1.0.0
#72Earlier quoted context omitted.
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.
A great way to stop identity politics becoming an issue is to bring it up unprompted through a throwaway account on Hacker News. Anonymously singling out specific members of the community that you dislike and labeling them as bad actors is particularly helpful.
Oh, wait...
Re: Io.js 1.0.0
#73I 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…
> es5 is a dinosaur as of today I don't think so. People publishing libraries in ES6 are asking for trouble. There are far too many half-complete ES6 implementations out there and compiling to ES5 definitely is the way to go (for libraries) unless there's a really compelling reason not to.
It looks like iojs is only going to ship features once they've shipped in Chrome without a flag. The compelling reason to use the features is that they're useful!
EDIT: I don't think anyone is going to be sympathetic to holding back from using conveniences because people are choosing to stick with an old runtime. It's a different ballgame than the browser.
Re: Io.js 1.0.0
#74Earlier 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.
I felt like he got thrown under the bus with that whole uproar, and was glad to see him in there.
Re: Io.js 1.0.0
#75Well, that escalated quickly.
Re: Io.js 1.0.0
#76I can unalias my `alias node=node --harmony` now!!
Re: Io.js 1.0.0
#77Tip 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…
> The main point seems to be that it's run on an open governance model
Ya, I think the main problem is that no one has any idea what that means from a practical sense. Will my code go faster? Will I get better support? etc.
Re: Io.js 1.0.0
#78Version 1.0.0 (Beta stability) The hell? Seems it's intentional: https://github.com/iojs/io.js/issues/251#issuecomment-694177...
They're sticking the strict semver with no tags, and explicitly wanted to abandon the 0.x version numbers, so the TC decided to do 1.0.0 as the first release but make it clear that it's not production ready.
Re: Io.js 1.0.0
#79Since there are features in Io that are neither in the current version nor planned for the future versions of Node, I guess Io.js should be explicitly specified as an engine in the package.json file of Io-specific modules. Tracking those modules will be a good metric of how well Io is received by the community.
Re: Io.js 1.0.0
#80Congratulations to the team who made this possible. Thanks for your hard work. Looking forward to switching binaries.