5 ms·

I guess io.js forced their hand.

by PLenz 12y ago

bhouston 12y ago
I think this is what IO.js wanted right? What were their other demands? It would be cool to see Node.JS and IO.js unified again and moving quickly forward. (I'm self interested because we essentially bet our company on Node/IO.)
- warfangle 12y ago
  Well, 0.12 has finally been released (after what, two years?) - so there's that.
- Thaxll 12y ago
  You bet your company on a single product that is 5 years old? :/
  - bhouston 12y ago
    Just like Facebook bet the company on PHP, not quite but you choose technologies and tend to stick with them for a while.
  - testrun 12y ago
    What are you using?
- wereHamster 12y ago
  Unlikely to happen. NodeJS has gone the enterprise way, which is to say that from now on it'll only receive bug/security fixes. It'll stay at the v8 version it is at today, so no new JavaScript features will be added to it (ie. no ES6/7). That's fine, apparently some people prefer that. Everybody else can switch to io.js and enjoy regular updates.
- nailer 12y ago
  > What were their other demands? The trademarks should be given to the foundation, like they are with, say Python and the Python Software Foundation.
- WalterSear 12y ago
  I don't think so. Io.js isn't a hand forcing - it's a horse bolting. Joyent's hand has been 'forced' to shut the barn door.
gangstead 12y ago
Hopefully they'll spoon io.js back into the node fold.
- tapsboy 12y ago
  I would rather like to see them continue operating like "be different, but together" so as to give a choice to users to either use the most cutting edge APIs or more stabler versions. Node.js could be like RHEL/Ubuntu LTS, where as IO.js could be like Fedora/Ubuntu Latest.
  - kbody 12y ago
    Exactly, I recently heard the nodeup podcast where it was said that io.js is beta and don't expect rc-1 or beta tag, just plain semver, but said that eventually both forks should unite again. That plus update-on-release V8s are incompatible with Joyent's "enterprise grade tested" releases. I like the two different ideas living together. A bit like: - Node.js: LTS - X: Public release - io.js: Beta/Canary
    - johnbellone 12y ago
      The only way that this will realistically work is if it falls under a single project. But hopefully the formation of this foundation will lead to a cohesive platform. Its fine if a small team or single developer runs a canary setup; at larger scale development it becomes very difficult to coordinate when its right to run LTS versus not. You'll always default to running what's on production.
  - gangstead 12y ago
    That's what's happened with Scala. Official Typesafe Scala is for enterprises and the fork by Typelevel is for faster development and experimentation, with a goal of contributing the things that work out back to main Scala (if Typesafe accepts the pull request).
    - kbody 12y ago

I guess io.js forced their hand.

by PLenz 12y ago

I guess io.js forced their hand.

I think this is what IO.js wanted right? What were their other demands? It would be cool to see Node.JS and IO.js unified again and moving quickly forward. (I'm self interested because we essentially bet our company on Node/IO.)

warfangle 12y ago
Well, 0.12 has finally been released (after what, two years?) - so there's that.
Thaxll 12y ago
You bet your company on a single product that is 5 years old? :/
- bhouston 12y ago
  Just like Facebook bet the company on PHP, not quite but you choose technologies and tend to stick with them for a while.
- testrun 12y ago
  What are you using?
wereHamster 12y ago
Unlikely to happen. NodeJS has gone the enterprise way, which is to say that from now on it'll only receive bug/security fixes. It'll stay at the v8 version it is at today, so no new JavaScript features will be added to it (ie. no ES6/7). That's fine, apparently some people prefer that. Everybody else can switch to io.js and enjoy regular updates.
nailer 12y ago
> What were their other demands? The trademarks should be given to the foundation, like they are with, say Python and the Python Software Foundation.
WalterSear 12y ago
I don't think so. Io.js isn't a hand forcing - it's a horse bolting. Joyent's hand has been 'forced' to shut the barn door.

gangstead 12y ago

Hopefully they'll spoon io.js back into the node fold.

tapsboy 12y ago
I would rather like to see them continue operating like "be different, but together" so as to give a choice to users to either use the most cutting edge APIs or more stabler versions. Node.js could be like RHEL/Ubuntu LTS, where as IO.js could be like Fedora/Ubuntu Latest.
- kbody 12y ago
  Exactly, I recently heard the nodeup podcast where it was said that io.js is beta and don't expect rc-1 or beta tag, just plain semver, but said that eventually both forks should unite again. That plus update-on-release V8s are incompatible with Joyent's "enterprise grade tested" releases. I like the two different ideas living together. A bit like: - Node.js: LTS - X: Public release - io.js: Beta/Canary
  - johnbellone 12y ago
    The only way that this will realistically work is if it falls under a single project. But hopefully the formation of this foundation will lead to a cohesive platform. Its fine if a small team or single developer runs a canary setup; at larger scale development it becomes very difficult to coordinate when its right to run LTS versus not. You'll always default to running what's on production.
- gangstead 12y ago
  That's what's happened with Scala. Official Typesafe Scala is for enterprises and the fork by Typelevel is for faster development and experimentation, with a goal of contributing the things that work out back to main Scala (if Typesafe accepts the pull request).
  - kbody 12y ago