5 ms·

They'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

They'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 ago
  It was node pre-Joyent
  - schmichael 11y ago
    There 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 ago
They 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.
tracker1 11y ago
With the io.js fork, the io.js open governance model, and advancements in the project moved significantly faster than NodeJS under Joyent. Since then the Node Foundation was created with a technical committee based on, and pretty much consisting of the io.js members with a few changes... Most of the technical advancements regarding the source are from the io.js branches. Node 0.12 included Intl support, one of the few features in Node that wasn't in io.js, with some contention about the size. The organization and releases will definitely be "Node" from 4.0 not io.js, the best guess is the movement of the branch happened ahead of updating the README file.

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 ago
It was node pre-Joyent
- schmichael 11y ago
  There 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 ago

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

tracker1 11y ago

With the io.js fork, the io.js open governance model, and advancements in the project moved significantly faster than NodeJS under Joyent. Since then the Node Foundation was created with a technical committee based on, and pretty much consisting of the io.js members with a few changes... Most of the technical advancements regarding the source are from the io.js branches. Node 0.12 included Intl support, one of the few features in Node that wasn't in io.js, with some contention about the size. The organization and releases will definitely be "Node" from 4.0 not io.js, the best guess is the movement of the branch happened ahead of updating the README file.