From the FAQ:
> What is io.js?
What does that even mean?
Edit: Thanks for those answering. I started figuring out what it was, but sometimes folks really need to learn that "A correct definition" is not the same as "a useful definition". However, if it's as cool as described, definitely might give it a shot.
Edit2: Is this expected to be as stable as Node.js consistently? And how solid is the upgrade path- is it going to be a pain upgrading between versions the way Node used to be, or is there a smoother upgrade process? I guess what I'm wondering is, do I get any benefit from using this right now, or would it be smart to still wait for whatever version they consider release quality?
Current Project Team Members
Isaac Z. Schlueter
For the record, I believe that's what should be written as the first answer on the FAQ (and maybe on the site's index.hml). The current one is atrocious.
Rather strange to see Fedor as a core team member in both projects, or at least one of them (likely node.js page) is out of date.
Yes I know, I need to add `s/anymore/yet`. But the statement is pretty much accurate. Its been almost 2 years since 0.11.0 was released and 0.12 is nowhere in sight.
Still, the inclusion shows that not all bridges are burned, which makes me happy.
So Ben Noorddhuis was a major contributor to NodeJS and a volunteer (that is, not a Joyent employee). It turns out Ben rejected a pull request that would have made pronoun in the document gender neutral. The documents were already grammatically correct, but whoever made the pull request had a political preference for using a non masculine pronoun. Ben rightly saw this a trivial change. But the political harpies made an issue of it. Joyent put an embarrassing and immature blog posting which essentially called Ben an "Asshole" and said that if he was an employee he'd be fired.
Ben, on the other hand, handled himself quite well.
The request is/was/remains a relevant one. Language is important, it is after all the one of the few tools to describe percieved reality.
a) Talk is cheap, action matters, and the PC police's main strategy is to complain until other people change, instead of enacting change themselves. Accommodating them is useless, they will simply find something new to complain about. Apologies are always insufficient, defiance is considered a declaration of war.
b) Language is indeed important, and redefining concepts like "privilege", "misogyny" and "harassment" to mean whatever the club of the perpetually offended thinks they mean is damaging to sane discourse.
It confuses me deeply that this fact could turn people off of the project regardless of its other practical and technical merits.
Mikeal is overtly political. Isaac is political from time to time since he's strongly aligned with the identity politics mob that attacked ben noordhuis back in the day. I really hope identity politics doesn't creep into the io.js governance.
That website needs serious work in terms of wording. Absolutely zero information on the website apart from the extremely vague tagline. I clicked a few links and all I could find was politics. Without the context given on HN I would still be wondering:
Is it a node.js replacement? Is it a NPM replacement? Is it a dog? Is it a cat? Can I eat it?
Even you want to sell something to people (even if that something is free as in beer) they need to know what that something is, first.
On the other hand, they've been saying that 0.12 will come out 'soon' for over a year, so this too may take longer than I expect.
By comparison, @nodejs announced on Dec 17th, 2014 that 0.11.15 was "tomorrow", but still haven't released anything: https://twitter.com/nodejs/status/545349270241435648
It's more like a new version of node with a different name to circumvent trademark issues.
io.js is a fork of node.js but is "better" because:
2) io.js is not controlled by private interests.
"Rails is just an implementation of the MVC pattern, not a framework."