4 ms·
Future Node.js releases will be from the io.js repo
- jinxedID 11y agoGood work! That happened way faster than I expected
- stringham 11y agoInteresting that they are moving forward with the name io.js rather than merging into node and keeping the legacy name.
- drunkcatsdgaf 11y agoI'm confused, I thought they were ditching io.js
- andreasklinger 11y agoI'd thought so too and assume the readmes havent been updated yet
- drunkcatsdgaf 11y agosee: https://github.com/nodejs/node/issues/2327 https://github.com/nodejs/node/issues/2327
- gregmac 11y agoIs anything even new here? The io.js README was last updated 18 days ago. Back in May, the two projects announced they were merging, and several things have been done in that respect: * The io.js project joined the Node Foundation (https://github.com/nodejs/node/issues/1664#issuecomment-101828384 https://github.com/nodejs/node/issues/1664#issuecomment-1018...). * Joyent transferred ownership of nodejs.org to the Linux Foundation (http://whois.icann.org/en/lookup?name=nodejs.org http://whois.icann.org/en/lookup?name=nodejs.org). It seems like the future-facing work is being done in the io.js repository.. that doesn't mean an eventual release from there will be called io.js. Can anyone link to anything more authoritative than a probably-not-updated README?
- lobster_johnson 11y agoI could be wrong, but I don't think they are renaming anything. They just replaced the official Node.js Github repo with the io.js repo, and it has the old readme. I expect the readme will be updated.
- mrks_ 11y agoIm surprised by this, too. Node is significantly more well-known than Io.
- EarlPoncho 11y agowhy
- schmichael 11y agoThey're really giving up one of the most recognizable platform names in tech (node.js)? Is this so Joyent can maintain control over its trademark? (However that implies they'll still use the name node.js for something.) Is there an explanation of why nodejs became iojs somewhere and not the reverse? (and whether code will be updated to remove "node" references?)
- mmanfrin 11y ago(Guessing) it is a signal to the community that node 'belongs' to the community -- hence renaming it after the community/nonjoyent fork.
- bdcravens 11y agoIt was node pre-Joyent
- schmichael 11y agoThere was no node pre-Joyent. Ryan Dahl and other early contributors were all working at Joyent. It is Joynet IP and they own the trademark.
- bdcravens 11y ago(sorry for delayed response) I don't think this is accurate. I don't know when Ryan went to work for node, but if you listen to his earliest talks, where he discusses the journey he took to develop node, it was an independent project. Additionally, these posts identify when Joyent took node under its umbrella (along with the IP): https://www.joyent.com/blog/a-new-abode-for-node/ https://www.joyent.com/blog/a-new-abode-for-node/ https://groups.google.com/forum/#!topic/nodejs/lWo0MbHZ6Tc https://groups.google.com/forum/#!topic/nodejs/lWo0MbHZ6Tc
- aikah 11y agoThey are not renaming anything. iojs is now the official source code of nodejs. I'm happy that the fork , led by the real maintainers of nodejs, is now the original project.
- deleted 11y ago[deleted]
- deleted 11y ago[deleted]
- mintplant 11y agoI think they just haven't updated the README yet.
- rmason 11y agoSomeone with business sense would rarely, if ever, kill a hot brand. Guessing that this wasn't really all that well thought through. Either that or there's some legal or trademark issue.
- tylermauthe 11y agoI can already see the jokes about this change from the Node Haters Club.
- obituary_latte 11y agoAs a non node/io user, I fail to compute your contribution to the discussion.
- tylermauthe 11y agoSame to you.
- deleted 11y ago[deleted]
- alrs 11y agoDetente is over, schism returns?
- RossDM 11y agoMisleading title, if you read the issue link that drunkcatsdgaf posted (https://github.com/nodejs/node/issues/2327 https://github.com/nodejs/node/issues/2327).
- Aldo_MX 11y agoSince no official statement has been made, I will just assume that they're arranging the repo.
- mattkrea 11y agoFuture Node.js releases will come from what is current io.js. That is all. The name is not changing. This is nothing to get excited about--this has been the plan all along.
- jameswyse 11y agoThe official name is Node.js. That repo is the combined source of Node.js 0.12 and io.js master and future releases will be coming from there. I think the next major release will be "Node.js v4.0.0"
- Killswitch 11y agoFor those wondering, this was a premature posting. Node.js is the name still, it's using io.js' source code from Node.js v4.0.0 and on. The Readme hasn't been updated yet.
- jshwlkr 11y agoNow I have to change my pinboard tags...
- lectrick 11y agoSomeone ping me when JS removes mutability.
- jessaustin 11y agoThis is a dumb posting with a really misleading title. Nowhere on the linked page does it say "Node.js/node is now io.js". Perhaps the maintainers should have updated the reamde before switching repos, but I suspect they're concentrating more on coding than on marketing.
- davorak 11y agoJust above the commit count: > Future Node.js releases will be from this repo. https://iojs.org https://iojs.org It is part of github's repo description.
- jessaustin 11y agoYes that is the title of this thread now. It is in some sense the converse of the original title that I quoted above.
- tracker1 11y agoThis blog post[1] should clear up a lot of the confusion... Most of this is just the transition of the organizational structure from io.js to the Node Foundation. https://medium.com/@nodesource/essential-steps-long-term-support-for-node-js-8ecf7514dbd https://medium.com/@nodesource/essential-steps-long-term-sup...
- dang 11y agoWe changed the title from "Node.js/node is now io.js". Submitters: please don't make up your own title on a post you didn't write. If you change it to something misleading, the entire thread can easily become about that, as here. Use the original title unless it is misleading or linkbait, and if necessary find some representative language in the OP.