Hacker News Reader

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

View on HN

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.

Have we heard yet when to expect the first merged release? I haven't found anywhere that its been stated.

Looks like they support up to 0.12.4 now.

https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/conce...

Good catch. The AMI I'm using could be outdated. I'll have to update later.

I had a problem where fibers was working on v0.12.3 with two applications, and when I deployed a third one with the regular "npm install && forever start" deal I got a "package did not self-register" issue that was only solved by rolling back to v0.10.36.

Reply on news.ycombinator.com