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.
Re:One Year with Node.js
by jessaustin on Tuesday June 16, 2015 @07:47PM
(#9729356)
...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?
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.
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.
Have we heard yet when to expect the first merged release? I haven't found anywhere that its been stated.
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.
So why didn't you publish anything about it? You've had tons of chances to make amends to the io.js community before the merge - a simple "I know what io.js is" tweet would have done it, or a blog post, or even a comment on the article or the HN discussion or reddit discussion it caused. Don't get me wrong, a lot of people deserve credit for the fantstic work on the merge (by mainly, people like mikeal) but don't think the community is not worried about the governance model or that people enjoy the fact the board sits above the TC, it's a necessity because projects need money but it's not like the community forgets why the split happened in the first place.
Respectfully, I never took from it that Scott didn't know what io.js was, rather that he knew and was being vocally dismissive.
How quickly did you guys expect to get treated like evil corporate overlords? I bet not this quickly.
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
[2] https://twitter.com/dshaw/status/610821802466639873