$> diff --es_staging (enable all completed harmony features)
> --harmony (enable all completed harmony features)
> --harmony_shipping (enable all shipped harmony fetaures)
> --harmony_modules (enable "harmony modules (implies block scoping)" (in progress))
> --harmony_arrays (enable "harmony array methods" (in progress))
> --harmony_array_includes (enable "harmony Array.prototype.includes" (in progress))
> --harmony_regexps (enable "harmony regular expression extensions" (in progress))
> --harmony_arrow_functions (enable "harmony arrow functions" (in progress))
> --harmony_proxies (enable "harmony proxies" (in progress))
> --harmony_sloppy (enable "harmony features in sloppy mode" (in progress))
> --harmony_unicode (enable "harmony unicode escapes" (in progress))
> --harmony_tostring (enable "harmony toString")
> --harmony_numeric_literals (enable "harmony numeric literals")
> --harmony_strings (enable "harmony string methods")
> --harmony_scoping (enable "harmony block scoping")
> --harmony_classes (enable "harmony classes (implies block scoping & object literal extension)")
> --harmony_object_literals (enable "harmony object literal extensions")
> --harmony_templates (enable "harmony template literals")Io.js 1.0.0
181–190 of 190 posts
Re: Io.js 1.0.0
#182Earlier quoted context omitted.
about 10, avatars of Vishnu. OTOH, Vishnu himself has a thousand names (Vishnu-Sahasra-nama)! I'd say you are in fairly good shape.
Haha, except mine is Rama like the spaceship :)
...which is named after the Hindu deity
Re: Io.js 1.0.0
#183Re: Io.js 1.0.0
#184Re: Io.js 1.0.0
#185I 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 mu…
> 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.
Though I'd imagine this will not hold true with addons, seeing as there are vastly different versions of the V8 engine.
Re: Io.js 1.0.0
#186Am I alone in being bemused and amused by this: Version 1.0.1 (Beta stability) Surely the main point of a 1.0 release is "stability" and to no longer be "beta"?
Not really, at least according to semver (which is what iojs uses). Stability of the API is denoted by a 1.x.x, it isn't necessarily an indication of the quality of the implementation, beta or otherwise. Node 0.12 was always being referred to as 'pretty much the 1.0 API', not calling it 1.x.x was a kind of 'get out of jail free' card in my opinion. So i'm glad the iojs team have least drawn a line in the sand and dec…
1.x is not really about stability either. To quote from the semver FAQ:
>How do I know when to release 1.0.0?
>If your software is being used in production, it should probably already be 1.0.0. If you have a stable API on which users have come to depend, you should be 1.0.0. If you're worrying a lot about backwards compatibility, you should probably already be 1.0.0.
Re: Io.js 1.0.0
#187"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.
Some npm modules require specific version of node. If iojs overwrites `node` you may see node-gyp use algernative fallback build, which causes installation failure. At least now, the better way is to keep symlink to node as node. Use iojs when needed.
Re: Io.js 1.0.0
#188Re: Io.js 1.0.0
#189In 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…
For posterity to anyone who still reads this, the spork thing is mostly my fault. And it sort of caught on.
I do website and irc stuff for io.js and I had trouble describing what the project was in relation to node.js.
So I called it a spork, because "sporks are friendlier". Whatever that means. Aside from being friendly.
Proof is somewhere in the io.js irc logs back near when the project sporked.
Re: Io.js 1.0.0
#190Earlier quoted context omitted.
An explanation about the downvotes would be appreciated. Thanks.
hu?
I know it is late but here is the explanation:
It was not my post and I care less about being downvoted and more about the problem that some people seems to prefer downvoting to explainating.
Downvoting, -in my opinion, is for things like redditism, clear breach of site guidelines etc. It is not for being uninformed (within reasonable limits) and certianly not for asking reasonable questions.