38 ms·

This is the same guy who said 'io.js, what's that?' And paid people not to switch... He's not fooling anyone http://readwrite.com/2015/02/03/joyent-nodejs-incub

by inglor 11y ago

This is the same guy who said 'io.js, what's that?' And paid people not to switch... He's not fooling anyone http://readwrite.com/2015/02/03/joyent-nodejs-incubator-iojs-node-io-fork http://readwrite.com/2015/02/03/joyent-nodejs-incubator-iojs... One more thing: Developers using IO instead of Node are, well, not invited. “IO.js, what’s that?” asked Joyent CEO Scott Hammond in response to my query about whether projects based on the fork would be able to enter. “This is a Node.js project for Node.js innovations.” "

bcantrill 11y ago
Disclaimer: I'm Joyent's CTO and I work for Scott. Normally I wouldn't comment on something on which I'm so obviously conflicted, but the record needs to be set straight on this point: Scott was taken entirely out of context by the reporter. In reference to the node.js incubator, the reporter (reasonably) asked about io.js. As an attempt at humor (albeit perhaps an ill advised one), Scott responded with: "IO.js -- what's that?" When there was an awkward silence, it was instantly clear to Scott that his attempt at humor had fallen flat -- and it was immediately clarified to the reporter that it was a joke: that he obviously knew what io.js was, and that the emphasis of the program was on node.js. That the reporter published the quote anyway (implying that Scott didn't, in fact, know what io.js was) was to take Scott grossly out of context. When we later asked ReadWriteWeb to clarify that Scott had been taken out of context, they flatly refused -- which is unfortunate, because it has resulted in heaps of undeserved abuse. (Many who have been involved with io.js have, in fact, gone out of their way to praise working with Scott.[1][2]) Now if I may inject my personal (if biased) opinion: the objective of the reporter was not to get the facts straight in this case, but rather to get eyeballs on the page -- ginning conflict if and as necessary. This is unfortunate, but it's not at all a surprise. It should also serve as a warning to all who engage with those who write about current events for a living: some (many, in fact) hold themselves up as journalists and work hard to get the story right -- but not all do, and one must be very careful, especially when attempting humor that might be deliberately taken out of context! [1] https://twitter.com/mikeal/status/555572909247574017 https://twitter.com/mikeal/status/555572909247574017 [2] https://twitter.com/dshaw/status/610821802466639873 https://twitter.com/dshaw/status/610821802466639873
- mattkrea 11y ago
  As much as I leaned toward the merger (running both in production sucks) I don't think people thought he was being serious--obviously he had to know what io.js was. Instead of being humorous it comes off as somewhat smug and ignoring a legitimate question or at least that's how I took it.
  - jessaustin 11y ago
    ...running both in production sucks... I'm sure it does. Can you describe the situation that has forced you to do this? Do you rely on modules that are limited to one or the other? Are those internal modules?
    - mattkrea 11y ago
      I simply haven't had the time to upgrade some but others are running on Elastic Beanstalk which is capped at Node 0.10.26 believe it or not. For newer things I'm running io.js 2.x and patiently waiting for the first merged release but wanted io.js for the ES6 functionality and IIRC Node 0.12.0 wasn't out yet.
      - netcraft 11y ago
        Have we heard yet when to expect the first merged release? I haven't found anywhere that its been stated.
      - mariusc23 11y ago
        Looks like they support up to 0.12.4 now. https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/concepts.platforms.html#concepts.platforms.nodejs https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/conce...
        mattkrea 11y ago
        Good catch. The AMI I'm using could be outdated. I'll have to update later.

by inglor 11y ago

bcantrill 11y ago

Disclaimer: I'm Joyent's CTO and I work for Scott. Normally I wouldn't comment on something on which I'm so obviously conflicted, but the record needs to be set straight on this point: Scott was taken entirely out of context by the reporter. In reference to the node.js incubator, the reporter (reasonably) asked about io.js. As an attempt at humor (albeit perhaps an ill advised one), Scott responded with: "IO.js -- what's that?" When there was an awkward silence, it was instantly clear to Scott that his attempt at humor had fallen flat -- and it was immediately clarified to the reporter that it was a joke: that he obviously knew what io.js was, and that the emphasis of the program was on node.js. That the reporter published the quote anyway (implying that Scott didn't, in fact, know what io.js was) was to take Scott grossly out of context. When we later asked ReadWriteWeb to clarify that Scott had been taken out of context, they flatly refused -- which is unfortunate, because it has resulted in heaps of undeserved abuse. (Many who have been involved with io.js have, in fact, gone out of their way to praise working with Scott.[1][2]) Now if I may inject my personal (if biased) opinion: the objective of the reporter was not to get the facts straight in this case, but rather to get eyeballs on the page -- ginning conflict if and as necessary. This is unfortunate, but it's not at all a surprise. It should also serve as a warning to all who engage with those who write about current events for a living: some (many, in fact) hold themselves up as journalists and work hard to get the story right -- but not all do, and one must be very careful, especially when attempting humor that might be deliberately taken out of context! [1] https://twitter.com/mikeal/status/555572909247574017 https://twitter.com/mikeal/status/555572909247574017 [2] https://twitter.com/dshaw/status/610821802466639873 https://twitter.com/dshaw/status/610821802466639873

mattkrea 11y ago
As much as I leaned toward the merger (running both in production sucks) I don't think people thought he was being serious--obviously he had to know what io.js was. Instead of being humorous it comes off as somewhat smug and ignoring a legitimate question or at least that's how I took it.
- jessaustin 11y ago
  ...running both in production sucks... I'm sure it does. Can you describe the situation that has forced you to do this? Do you rely on modules that are limited to one or the other? Are those internal modules?
  - mattkrea 11y ago
    I simply haven't had the time to upgrade some but others are running on Elastic Beanstalk which is capped at Node 0.10.26 believe it or not. For newer things I'm running io.js 2.x and patiently waiting for the first merged release but wanted io.js for the ES6 functionality and IIRC Node 0.12.0 wasn't out yet.
    - netcraft 11y ago
      Have we heard yet when to expect the first merged release? I haven't found anywhere that its been stated.
    - mariusc23 11y ago
      Looks like they support up to 0.12.4 now. https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/concepts.platforms.html#concepts.platforms.nodejs https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/conce...
      - mattkrea 11y ago
        Good catch. The AMI I'm using could be outdated. I'll have to update later.