9 ms·

Io.js 1.3.0 released

158 points by antouank 12y ago

scrapcode 12y ago
> 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).
- phpnode 12y ago
  HN auto-capitalizes story titles, because it presumes to know better than the submitter.
  - tedunangst 12y ago
    Can't have people just running around disregarding the rules. Think how disruptive that would be.
    - qooleot 12y ago
      No Soup for You! https://www.youtube.com/watch?v=svSGKJFSl-8 https://www.youtube.com/watch?v=svSGKJFSl-8
    - chris_wot 12y ago
      I'd step carefully here, because you really don't want to accidentally mention semicolons...
  - maxerickson 12y ago
    This is wrong. There's stories in new at the moment that start with a lowercase letter, and this story has a lowercase word in the title. There's apparently immense social pressure to capitalize titles, but it isn't enforced by HN.
    - silverwind 12y ago
      It seems there is some kind of job that regularily changes titles to upper case. We had that happen on the io.js 1.0 thread.
- keslag 12y ago
  The official name of Io.js in English is Io.js as it's a name, it is stylized as io.js. In Canada here, we have a company Telus, which stylizes it's name as TELUS. However, when discussing the company in non-marketing environments, such as Wikipedia, it's called Telus. The rules for English trump a creators stylization rules in many situations.
  - phpnode 12y ago
    No, the official name for io.js is io.js, it is explicitly not Io.js. You can tell because this is what the owners of the project have clearly stated. Linguistic rules (which are rarely in fact rules), have nothing to do with it. If I tell you my name is "bob" and not "Bob" then I'm right because it's my name, you don't get to enforce your own preferences, just because of the language you speak.
    - DanBC 12y ago
      But if you were to call yourself bob you should not be surprised when everyone mispells your name as Bob.
      - phpnode 12y ago
        No, it shouldn't be surprising, but they are not correct, because bob is my name (it isn't).
        jsmeaton 12y ago
        If I started a sentence with your name though, I would capitalise the name. Bob went to the shop. When he got there, bob bought an icecream.
  - integraton 12y ago
    That's not true at all. You shouldn't capitalize a brand name like iPhone, for example. http://english.stackexchange.com/a/9065 http://english.stackexchange.com/a/9065
- nailer 12y ago
  I wouldn't capitalise it either, but do you refer to Yahoo! and NVIDIA consistently with their own branding guidelines?
  - Argorak 12y ago
    Yahoo uses "Yahoo" outside of their logo. So, usually, yes.
3princip 12y ago
What is the reasoning behind the version jumps? 1.0.3->1.0.4->1.2.0->1.3.0 Sure, it's just a number, but the changelog isn't that big. Version inflation for no particular reason, apart from marketing, seems a bit silly. What am I missing?
- phpnode 12y ago
  http://semver.org/ http://semver.org/
  - 3princip 12y ago
    I've probably been conditioned by nodejs versioning . I guess this makes sense. Still feels strange.
    - phpnode 12y ago
      yeah, node doesn't do this. node 0.12.0 should actually be (at least) node 5.0, if they followed semver.
      - riffraff 12y ago
        I think religious following of semver doesn't matter, but semver says that pre 1.0 numbers are essentially meaningless so nodejs might be actually following it correctly. > Major version zero (0.y.z) is for initial development. Anything may change at any time. The public API should not be considered stable.
        phpnode 12y ago
        I think not: > 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.
        12y ago
deleted 12y ago
[deleted]
nailer 12y ago
Good stuff: RC4 is officially removed from the (edit: default set of, thanks ewegrump) cipher suites. Some background: https://community.qualys.com/blogs/securitylabs/2013/03/19/rc4-in-tls-is-broken-now-what https://community.qualys.com/blogs/securitylabs/2013/03/19/r...
- ewegrump 12y ago
  It's not removed, it's just not in the default list anymore. You can re-enable it with an option if you really do care.
  - silverwind 12y ago
    Correct, RC4 will still be supported until OpenSSL drops it, which is probably never.
CmonDev 12y ago
So the Node.js is dead now?
- falcolas 12y ago
  Doesn't seem like it, it's just the "RHEL" edition when compared to "Fedora" - slower, steadier release pace that focuses on stability, not features. EDIT: Downvotes ahoy. Let's be honest here. Stable code (especially stable threaded code) requires QA time after adding new features. There are commits in this release which are less than 5 days old. 5 days is not enough time to shake out bugs. Given that the developers are human, unit tests are incapable of finding all issues, and QA resources cost money, there is no way that this release could be considered to be stable. A company would deploy this at their own risk, knowing that it's likely to have bugs which will have to be reported and fixed. Not all companies can afford to take on that kind of risk, ergo a release like Node.js, which trails behind the bleeding edge of these technologies, makes sense to exist.
  - oe 12y ago
    To be fair io.js also focuses on stability and communicating the stability through proper use of semantic versioning. It's not like io.js wouldn't be production ready.
    - mrcwinn 12y ago
      A versioning system does not ensure stability. Moving quickly in software generally means less stability over time, semantic versioning or not.
      - okal 12y ago
        > "Moving quickly in software generally means less stability over time..." Rather broad statement, that. Care to qualify it?
        mrcwinn 12y ago
miralabs 12y ago
Isaac Schleuter and Mikeal Rogers was recently in Javascript Jabber talking about io.js and mostly answers questions below. http://devchat.tv/js-jabber/147-jsj-io-js-with-isaac-schleuter-and-mikeal-rogers http://devchat.tv/js-jabber/147-jsj-io-js-with-isaac-schleut...
shadowmint 12y ago
Nice, but to be fair, nothing much to see here. Another point release, the future marches on, Node continues to fall behind. Everyone happily continues to not care what happens to it as the Node foundation... does whatever it is it's doing. We don't all need to get up and clap every two weeks when they release a new version; this should just be life as normal really.
- deleted 12y ago
  [deleted]
- general_failure 12y ago
  Do you know any major player supporting iojs? Like aws, heroku.
  - neiled 12y ago
    heroku is: https://devcenter.heroku.com/changelog-items/595 https://devcenter.heroku.com/changelog-items/595
  - kin 12y ago
    the major player I'd say would be the community
- steveklabnik 12y ago
  This is an interesting side effect of the 'release train' model. Releases used to be a big deal, but for many projects, they're not a big deal anymore. It's really nice from an engineering perspective, but it reduces your ability to market in the same way as before.
adamkochanowicz 12y ago
So what is the NPM of io.js?
- joe_momma 12y ago
  it's still NPM, even comes with io.js download. Works just like Node.
- deleted 12y ago
  [deleted]
- wildpeaks 12y ago
  If you mean which version, the changelog says version 2.5.1 in that release. If you're asking if io.js is using a different npm, no it's using the same as Node. You use io.js pretty much like "another version of node" which is why you'd use nvm if you want to have both io and node on the same system (same way you'd use nvm to have two versions of node on the same system) or just straight upgrade/replace, like replacing 0.10 by 0.12.
- Fishrock123 12y ago
  npm stands for "no problem meatbag", not "node package manager" ;) It's the package manager for javascript and will continue to be. The module system in io.js is not going to be changing anytime soon.
bjackman 12y ago
External curious observer (don't do anything Node-related) here. Hadn't heard of io.js before. Interesting. Is this genuinely more popular than Node, or is this one of those cases where the HN crowd is skewed in its favour? Does it look like it'll take over as the standard server-side async JS system? Also how close is it to being a drop-in replacement for Node?
- jchook 12y ago
  My understanding is that the original developers of node left the project to create io.js, a derivative with a different set of values and goals. See https://iojs.org/en/faq.html https://iojs.org/en/faq.html and https://iojs.org/en/es6.html https://iojs.org/en/es6.html
- bceagle 12y ago
  Check out this episode of JavaScript Jabber for a good explanation of io.js: http://devchat.tv/js-jabber/147-jsj-io-js-with-isaac-schleuter-and-mikeal-rogers http://devchat.tv/js-jabber/147-jsj-io-js-with-isaac-schleut... tl;dr is that all the core contributors outside Joyent started working on io.js with an open governance model. Everyone wants to join back together but only after Joyent agrees to put node under the same governance model.
- silverwind 12y ago
  It's a 0.12 drop-in replacement with some minor API enhancements and a lot of bug fixes. Also, all current v8 ES6 features are enabled in io.js by default, while they still require the --harmony flag on node.
  - tracker1 12y ago
    Not all of the features, just those marked as stable in v8.
mike_ivanov 12y ago
I've read the Changelog, the Readme and the FAQ, and I still don't understand what is it. Am I an idiot?
- mike_ivanov 12y ago
  Instead of downvoting, could you please explain? All I see there is some node-but-not-so-joyenty stuff without much substance. What is the problem being solved?
  - seppo0010 12y ago
    Read the other comments: https://news.ycombinator.com/item?id=9081053 https://news.ycombinator.com/item?id=9081053
    - mike_ivanov 12y ago
      Why that is not a part of the Readme/FAQ?
      - hibbelig 12y ago
        You're looking at the Changelog. The README is next door, and it explains: > This repository began as a GitHub fork of joyent/node. > io.js contributions, releases, and contributorship are under an open governance model. We intend to land, with increasing regularity, releases which are compatible with the npm ecosystem that has been built to date for Node.js.
        mike_ivanov 12y ago
        That doesn't tell me anything. It assumes the reader is somehow familiar with the context and shares the authors' sentiment, although that is not true. This is what should be explained there: 1. What is the problem with Node.js? 2. What is wrong with Joyent? 3. Why the fork was the only adequate solution? 4. How come this is beneficial (and not harmful) to the community? 5. Is it a drop-in replacement? How does it affect existing projects? 6. How the future looks like from this point of view? However hard I look at that paragraph in Readme, I still can't see these questions answered. Edit: typo

158 points by antouank 12y ago

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

phpnode 12y ago
HN auto-capitalizes story titles, because it presumes to know better than the submitter.
- tedunangst 12y ago
  Can't have people just running around disregarding the rules. Think how disruptive that would be.
  - qooleot 12y ago
    No Soup for You! https://www.youtube.com/watch?v=svSGKJFSl-8 https://www.youtube.com/watch?v=svSGKJFSl-8
  - chris_wot 12y ago
    I'd step carefully here, because you really don't want to accidentally mention semicolons...
- maxerickson 12y ago
  This is wrong. There's stories in new at the moment that start with a lowercase letter, and this story has a lowercase word in the title. There's apparently immense social pressure to capitalize titles, but it isn't enforced by HN.
  - silverwind 12y ago
    It seems there is some kind of job that regularily changes titles to upper case. We had that happen on the io.js 1.0 thread.
keslag 12y ago
The official name of Io.js in English is Io.js as it's a name, it is stylized as io.js. In Canada here, we have a company Telus, which stylizes it's name as TELUS. However, when discussing the company in non-marketing environments, such as Wikipedia, it's called Telus. The rules for English trump a creators stylization rules in many situations.
- phpnode 12y ago
  No, the official name for io.js is io.js, it is explicitly not Io.js. You can tell because this is what the owners of the project have clearly stated. Linguistic rules (which are rarely in fact rules), have nothing to do with it. If I tell you my name is "bob" and not "Bob" then I'm right because it's my name, you don't get to enforce your own preferences, just because of the language you speak.
  - DanBC 12y ago
    But if you were to call yourself bob you should not be surprised when everyone mispells your name as Bob.
    - phpnode 12y ago
      No, it shouldn't be surprising, but they are not correct, because bob is my name (it isn't).
      - jsmeaton 12y ago
        If I started a sentence with your name though, I would capitalise the name. Bob went to the shop. When he got there, bob bought an icecream.
- integraton 12y ago
  That's not true at all. You shouldn't capitalize a brand name like iPhone, for example. http://english.stackexchange.com/a/9065 http://english.stackexchange.com/a/9065
nailer 12y ago
I wouldn't capitalise it either, but do you refer to Yahoo! and NVIDIA consistently with their own branding guidelines?
- Argorak 12y ago
  Yahoo uses "Yahoo" outside of their logo. So, usually, yes.

3princip 12y ago

What is the reasoning behind the version jumps? 1.0.3->1.0.4->1.2.0->1.3.0 Sure, it's just a number, but the changelog isn't that big. Version inflation for no particular reason, apart from marketing, seems a bit silly. What am I missing?

phpnode 12y ago
http://semver.org/ http://semver.org/
- 3princip 12y ago
  I've probably been conditioned by nodejs versioning . I guess this makes sense. Still feels strange.
  - phpnode 12y ago
    yeah, node doesn't do this. node 0.12.0 should actually be (at least) node 5.0, if they followed semver.
    - riffraff 12y ago
      I think religious following of semver doesn't matter, but semver says that pre 1.0 numbers are essentially meaningless so nodejs might be actually following it correctly. > Major version zero (0.y.z) is for initial development. Anything may change at any time. The public API should not be considered stable.
      - phpnode 12y ago
        I think not: > 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.
        12y ago

deleted 12y ago

[deleted]

nailer 12y ago

Good stuff: RC4 is officially removed from the (edit: default set of, thanks ewegrump) cipher suites. Some background: https://community.qualys.com/blogs/securitylabs/2013/03/19/rc4-in-tls-is-broken-now-what https://community.qualys.com/blogs/securitylabs/2013/03/19/r...

ewegrump 12y ago
It's not removed, it's just not in the default list anymore. You can re-enable it with an option if you really do care.
- silverwind 12y ago
  Correct, RC4 will still be supported until OpenSSL drops it, which is probably never.

CmonDev 12y ago

So the Node.js is dead now?

falcolas 12y ago
Doesn't seem like it, it's just the "RHEL" edition when compared to "Fedora" - slower, steadier release pace that focuses on stability, not features. EDIT: Downvotes ahoy. Let's be honest here. Stable code (especially stable threaded code) requires QA time after adding new features. There are commits in this release which are less than 5 days old. 5 days is not enough time to shake out bugs. Given that the developers are human, unit tests are incapable of finding all issues, and QA resources cost money, there is no way that this release could be considered to be stable. A company would deploy this at their own risk, knowing that it's likely to have bugs which will have to be reported and fixed. Not all companies can afford to take on that kind of risk, ergo a release like Node.js, which trails behind the bleeding edge of these technologies, makes sense to exist.
- oe 12y ago
  To be fair io.js also focuses on stability and communicating the stability through proper use of semantic versioning. It's not like io.js wouldn't be production ready.
  - mrcwinn 12y ago
    A versioning system does not ensure stability. Moving quickly in software generally means less stability over time, semantic versioning or not.
    - okal 12y ago
      > "Moving quickly in software generally means less stability over time..." Rather broad statement, that. Care to qualify it?
      - mrcwinn 12y ago

miralabs 12y ago

Isaac Schleuter and Mikeal Rogers was recently in Javascript Jabber talking about io.js and mostly answers questions below. http://devchat.tv/js-jabber/147-jsj-io-js-with-isaac-schleuter-and-mikeal-rogers http://devchat.tv/js-jabber/147-jsj-io-js-with-isaac-schleut...

shadowmint 12y ago

Nice, but to be fair, nothing much to see here. Another point release, the future marches on, Node continues to fall behind. Everyone happily continues to not care what happens to it as the Node foundation... does whatever it is it's doing. We don't all need to get up and clap every two weeks when they release a new version; this should just be life as normal really.

deleted 12y ago
[deleted]
general_failure 12y ago
Do you know any major player supporting iojs? Like aws, heroku.
- neiled 12y ago
  heroku is: https://devcenter.heroku.com/changelog-items/595 https://devcenter.heroku.com/changelog-items/595
- kin 12y ago
  the major player I'd say would be the community
steveklabnik 12y ago
This is an interesting side effect of the 'release train' model. Releases used to be a big deal, but for many projects, they're not a big deal anymore. It's really nice from an engineering perspective, but it reduces your ability to market in the same way as before.

adamkochanowicz 12y ago

So what is the NPM of io.js?

joe_momma 12y ago
it's still NPM, even comes with io.js download. Works just like Node.
deleted 12y ago
[deleted]
wildpeaks 12y ago
If you mean which version, the changelog says version 2.5.1 in that release. If you're asking if io.js is using a different npm, no it's using the same as Node. You use io.js pretty much like "another version of node" which is why you'd use nvm if you want to have both io and node on the same system (same way you'd use nvm to have two versions of node on the same system) or just straight upgrade/replace, like replacing 0.10 by 0.12.
Fishrock123 12y ago
npm stands for "no problem meatbag", not "node package manager" ;) It's the package manager for javascript and will continue to be. The module system in io.js is not going to be changing anytime soon.

bjackman 12y ago

External curious observer (don't do anything Node-related) here. Hadn't heard of io.js before. Interesting. Is this genuinely more popular than Node, or is this one of those cases where the HN crowd is skewed in its favour? Does it look like it'll take over as the standard server-side async JS system? Also how close is it to being a drop-in replacement for Node?

jchook 12y ago
My understanding is that the original developers of node left the project to create io.js, a derivative with a different set of values and goals. See https://iojs.org/en/faq.html https://iojs.org/en/faq.html and https://iojs.org/en/es6.html https://iojs.org/en/es6.html
bceagle 12y ago
Check out this episode of JavaScript Jabber for a good explanation of io.js: http://devchat.tv/js-jabber/147-jsj-io-js-with-isaac-schleuter-and-mikeal-rogers http://devchat.tv/js-jabber/147-jsj-io-js-with-isaac-schleut... tl;dr is that all the core contributors outside Joyent started working on io.js with an open governance model. Everyone wants to join back together but only after Joyent agrees to put node under the same governance model.
silverwind 12y ago
It's a 0.12 drop-in replacement with some minor API enhancements and a lot of bug fixes. Also, all current v8 ES6 features are enabled in io.js by default, while they still require the --harmony flag on node.
- tracker1 12y ago
  Not all of the features, just those marked as stable in v8.

mike_ivanov 12y ago

I've read the Changelog, the Readme and the FAQ, and I still don't understand what is it. Am I an idiot?

mike_ivanov 12y ago
Instead of downvoting, could you please explain? All I see there is some node-but-not-so-joyenty stuff without much substance. What is the problem being solved?
- seppo0010 12y ago
  Read the other comments: https://news.ycombinator.com/item?id=9081053 https://news.ycombinator.com/item?id=9081053
  - mike_ivanov 12y ago
    Why that is not a part of the Readme/FAQ?
    - hibbelig 12y ago
      You're looking at the Changelog. The README is next door, and it explains: > This repository began as a GitHub fork of joyent/node. > io.js contributions, releases, and contributorship are under an open governance model. We intend to land, with increasing regularity, releases which are compatible with the npm ecosystem that has been built to date for Node.js.
      - mike_ivanov 12y ago
        That doesn't tell me anything. It assumes the reader is somehow familiar with the context and shares the authors' sentiment, although that is not true. This is what should be explained there: 1. What is the problem with Node.js? 2. What is wrong with Joyent? 3. Why the fork was the only adequate solution? 4. How come this is beneficial (and not harmful) to the community? 5. Is it a drop-in replacement? How does it affect existing projects? 6. How the future looks like from this point of view? However hard I look at that paragraph in Readme, I still can't see these questions answered. Edit: typo