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!
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?
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.
https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/conce...
How quickly did you guys expect to get treated like evil corporate overlords? I bet not this quickly.
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.” "