6 ms·

They will probably release a merged version in October which will be named Node.js 4.0 and will be supported for 2,5 years. https://medium.com/@nodesource/esse

by slasaus 11y ago

They will probably release a merged version in October which will be named Node.js 4.0 and will be supported for 2,5 years. https://medium.com/@nodesource/essential-steps-long-term-support-for-node-js-8ecf7514dbd https://medium.com/@nodesource/essential-steps-long-term-sup...

rrss1122 11y ago
Ah, seems version skipping is all the rage nowadays. Having an LTS version will be welcome though. Having to go in there and upgrade node every few months is a mild inconvenience on my project.
- mattkrea 11y ago
  It isn't skipping versions. io.js is strictly following semver and have introduced breaking changes (usually due to a V8 upgrade) in each major bump.
  - coroutines 11y ago
    Ah, seems semantic versioning is all the rage nowadays.* Fixed it!
    - serve_yay 11y ago
      Yeah, having your version numbers mean something? What'll those wacky JS hipsters come up with next?!
wukerplank 11y ago
If that is true: That's just an odd jump, seeing that Node's current version is 0.12.7
- LukeB_UK 11y ago
  It'll be version 4 because it'll be a continuation from version 3 of io.js
  - wukerplank 11y ago
    I understand that. But in my understanding a version number also reflects where a project stands in respect to features planned vs features implemented. Jumping from 0.x to 4.x is plain weird in this regard.
    - grandalf 11y ago
      you must not have been following the IO.js saga so far... first they forked node, then began using semver, and very quickly got to 2.x and now 3.x. Merging with node just means now anyone using node can use whichever version they want, and future versions are officially part of node.
    - seiji 11y ago
      But in my understanding a version number also reflects where a project stands in respect to features planned vs features implemented. Nope. Version numbers are completely arbitrary. Firefox is on version 39 and Chrome is on 46.0.2471.2 and Safari is on version 8.0.6 and Webkit is on version 10600.6.3. Windows 3.1 was followed by Windows 95 was followed by Windows 2000 was followed by Windows 7 was followed by Windows 10?
      - yellowapple 11y ago
        Hell, TeX version numbers are just additional digits of pi (latest version is 3.14159265), and Slackware jumped version numbers from 4 to 7 because people kept thinking it lagged behind Debian's whole-number versioning (ultimately, Slackware's version numbers would have surpassed Debian's even without the artificial bump, but whatever). Arbitrary indeed.
        seiji 11y ago
        Exactly. Their rationale is TeX can only become more perfect over time.

by slasaus 11y ago

rrss1122 11y ago

Ah, seems version skipping is all the rage nowadays. Having an LTS version will be welcome though. Having to go in there and upgrade node every few months is a mild inconvenience on my project.

mattkrea 11y ago
It isn't skipping versions. io.js is strictly following semver and have introduced breaking changes (usually due to a V8 upgrade) in each major bump.
- coroutines 11y ago
  Ah, seems semantic versioning is all the rage nowadays.* Fixed it!
  - serve_yay 11y ago
    Yeah, having your version numbers mean something? What'll those wacky JS hipsters come up with next?!

wukerplank 11y ago

If that is true: That's just an odd jump, seeing that Node's current version is 0.12.7

LukeB_UK 11y ago
It'll be version 4 because it'll be a continuation from version 3 of io.js
- wukerplank 11y ago
  I understand that. But in my understanding a version number also reflects where a project stands in respect to features planned vs features implemented. Jumping from 0.x to 4.x is plain weird in this regard.
  - grandalf 11y ago
    you must not have been following the IO.js saga so far... first they forked node, then began using semver, and very quickly got to 2.x and now 3.x. Merging with node just means now anyone using node can use whichever version they want, and future versions are officially part of node.
  - seiji 11y ago
    But in my understanding a version number also reflects where a project stands in respect to features planned vs features implemented. Nope. Version numbers are completely arbitrary. Firefox is on version 39 and Chrome is on 46.0.2471.2 and Safari is on version 8.0.6 and Webkit is on version 10600.6.3. Windows 3.1 was followed by Windows 95 was followed by Windows 2000 was followed by Windows 7 was followed by Windows 10?
    - yellowapple 11y ago
      Hell, TeX version numbers are just additional digits of pi (latest version is 3.14159265), and Slackware jumped version numbers from 4 to 7 because people kept thinking it lagged behind Debian's whole-number versioning (ultimately, Slackware's version numbers would have surpassed Debian's even without the artificial bump, but whatever). Arbitrary indeed.
      - seiji 11y ago
        Exactly. Their rationale is TeX can only become more perfect over time.