Can this be installed with Node side-by-side or does it take over the `node` name?
It gets symlinked to node and npm
Io.js 1.0.0
161–170 of 190 posts
Re: Io.js 1.0.0
#162Earlier quoted context omitted.
I still cannot figure out what this actually is besides Javascript
It's an implementation of the Reactor Pattern with some package management capability. Not a platform. Not a framework. Not an engine. Just a script.
You could literally say that about anything.
"Rails is just an implementation of the MVC pattern, not a framework."
Re: Io.js 1.0.0
#163In their words, io.js is "A spork of Node.js with an open governance model". Hmm. Lets hope the spork gets spooned so that no projects get knifed. If not then I guess we have to hope for a knork so we don't get stuck with a couple of chopsticks. Glossary Forking : Creating a fork to intentionally diverge from main-line development. Spooning : Merging a fork back into the main line of a project Sporking : Creating a f…
Lets hope they keep momentum, otherwise they'll be 'corkscrewing' the community!
Re: Io.js 1.0.0
#164Any advice on whether it's better to use ES6 or Coffeescript?
First of all they're not the same thing. Coffeescript transpiles to JS (ES3 or 4 if I remember well) and ES6 is a new standard (not finished yet). Maybe one day coffee may compile to ES6 (but that's not likely since that would break support with older browsers). As said before, ES6 may reduce the need of transpiled languages but won't replace them. From my point of view, ES6 will never replace ClojureScript nor TypeS…
Support for generators has been merged into Coffeescript master — https://github.com/jashkenas/coffeescript/pull/3240
Re: Io.js 1.0.0
#165Earlier quoted context omitted.
I don't see truth in your statement that core people did not want to defend him. Shitstorm happened mostly by outsiders/ignorants. He didn't want to continue in such a climate. Joyent wrote a blog post that ruined their reputation. - Good net effect one year later is that node might free themself from Joyent and become much more open/inclusive.
Could someone make (or provide a link to) a summary of the melodrama for outsiders ? It being not too partisan for one side or the other would be a plus.
I was interested myself, so I did a little google-foo.
So Ben Noorddhuis was a major contributor to NodeJS and a volunteer (that is, not a Joyent employee). It turns out Ben rejected a pull request that would have made pronoun in the document gender neutral. The documents were already grammatically correct, but whoever made the pull request had a political preference for using a non masculine pronoun. Ben rightly saw this a trivial change. But the political harpies made an issue of it. Joyent put an embarrassing and immature blog posting which essentially called Ben an "Asshole" and said that if he was an employee he'd be fired. https://www.joyent.com/blog/the-power-of-a-pronoun Ben, on the other hand, handled himself quite well. https://github.com/joyent/libuv/pull/1015#issuecomment-29568... https://news.ycombinator.com/item?id=6845286
Re: Io.js 1.0.0
#166Earlier quoted context omitted.
Really? I thought V8 makes JavaScript run on a server.
no, V8 makes javascript run, iojs makes javascript run on server.
So it's useless without V8. I mean I can install Chrome or an Awesomium app onto server and it will also run JavaScript on server (via V8).
Re: Io.js 1.0.0
#167OP: sorry to nitpick, but the proper capitalization is 'io.js'.
Actually, it's both io.js or Io.js. The one that got canned was IO.js.
From https://github.com/iojs/io.js
> Is it io.js or IO.js or iojs or IOjs or iOjS?
> The official name is io.js, which should never be capitalized, especially not at the start of a sentence, unless it is being displayed in a location that is customarily all-caps (such as the title of man pages.)
Re: Io.js 1.0.0
#168Node got forked because it got corped. When a corporation sinks their hooks into an active open source project, it's only a matter of time. Mysql, Maria, Hudson, Jenkins... same story. io.js is the way forward, and congrats to the core team.
Plenty of corporations have successfully managed open-source projects.
Yes. And I wouldn't compare Joyent with Oracle.
Re: Io.js 1.0.0
#169Earlier 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.
Except "identity politics" aka inclusiveness are at the heart of their open governance model... Or did you miss the drama over their code of conduct; that they were going to one and how they solicited and followed advice from noted social justice advocates in drafting it.
It confuses me deeply that this fact could turn people off of the project regardless of its other practical and technical merits.
Re: Io.js 1.0.0
#170In their words, io.js is "A spork of Node.js with an open governance model". Hmm. Lets hope the spork gets spooned so that no projects get knifed. If not then I guess we have to hope for a knork so we don't get stuck with a couple of chopsticks. Glossary Forking : Creating a fork to intentionally diverge from main-line development. Spooning : Merging a fork back into the main line of a project Sporking : Creating a f…
groan Don't get me wrong, thanks for the information. But seriously. It's like when you come up with a whimsical naming scheme for your home network devices and you get trapped in that naming scheme and have to come up with more and more obscure Lithuanian folk demons that fit into your conventions and it becomes a parody of itself and you're not sure if you're serious or joking anymore.
I named my new external drive "Rama". Not sure how far I can take that, though.