61–70 of 190 posts
OP: 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.
Earlier 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.
...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,…
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
Congratulations to the io.js team! I look forward to future releases. Specifically, no longer having to use --harmony_arrow_functions.
...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.
how would one go about deploying (say on Heroku) an iojs app?
(screencast: https://twitter.com/HunterLoftis/status/555234067520565249)
We're also excited to see node hit a 1.0 and merge in new V8, ES6 features, etc. I'm especially excited about Cluster's round-robin load balancing which has been a compelling reason to use 'unstable 0.11' for a while.
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…
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.
Congratulations to the io.js team! I look forward to future releases. Specifically, no longer having to use --harmony_arrow_functions.
Ugh, please don't use that. The semantics of --harmony_arrow_functions are totally different from real arrow functions. Your code will break horribly.