6 ms·

Having just started learning about and using node, I read this release note and then this made me say to myself, "What the fuck?" [15:39 user@host ~] > node -v

by cdubzzz 11y ago

Having just started learning about and using node, I read this release note and then this made me say to myself, "What the fuck?" [15:39 user@host ~] > node -v v0.10.25

_RPM 11y ago
Using your distributions package manager you'll get the older versions. I'm guessing you're using Ubuntu? Better off just compiling from source.
- dahjelle 11y ago
  You can also use nodebrew[1], which also allows you to install multiple versions in parallel. [1] https://github.com/hokaccha/nodebrew https://github.com/hokaccha/nodebrew
  - brokentone 11y ago
    I prefer n[1], but others might like nvm[2] which is quite similar to rvm. [1] https://github.com/tj/n https://github.com/tj/n [2] https://github.com/creationix/nvm https://github.com/creationix/nvm
amccloud 11y ago
Node jumped from v0.x to v4.x when iojs merged back into node (something like a month ago)
- bdcravens 11y ago
  Do note that even before that, node was on 0.12, and 0.10.25 is from April 2014.
coldtea 11y ago
>Having just started learning about and using node, I read this release note and then this made me say to myself, "What the fuck?" If you've started learning node, then it probably makes sense to follow the community portals and news too. In which case you'd known about io.js and the 4.x thing. In other words, get into the whole project / community / culture.
- yincrash 11y ago
  Not everyone has time to get into an entire community / culture when they just need to use tools.
  - bdcravens 11y ago
    I think monitoring the repository for an open source project you depend on is critical. Even if you're not trying to be cutting edge, we have several years of security incidents that tell us that you can't turn a blind eye.
  - coldtea 11y ago
    On the contrary. It's when you need to use the tools when you most have to get into the community/culture. If you just wanna learn something as a hobby, have fun, etc, then you don't have to do anything. But knowing about the product, its community and its release roadmap is essential for anything you want to use to put something in production. Actually it's essential for even considering to use this technology over another. And I wont even get into security and stability issues that a closer look at the project will make you aware of sooner.
- watson 11y ago
  a LOT of stuff have happened in the Node community over a very short period of time. So it's understandable that not everyone have had the resources to follow everything :) Especially if you're just getting started and not using Node full time yet.
- elros 11y ago
  > In other words, get into the whole project / community / culture. Could you elaborate on that? Which resources do you think would be useful to be followed to get into the culture and community?
  - coldtea 11y ago
    1) At the very least, read the projects About Us/History page, and its Wikipedia article, to get a sense where it stands for in the grand scheme of things. 2) Do some searching to see what alternatives exist. Even typing "alternative to Node.js" will give you some starting points. E.g. when you find out about NW.js and want to use it, it would pay to know that there's also Electron. If you learn there's this hot Angular thing, it should pay to also check React and Ember. 3) Also check how "alive" the project is. Things like GitHub followers, latest commits, release frequency, etc, will give you a sense of that. You don't have to go wild with this and (2) -- just check the 2-3 more prevalent projects in your niche. Again, if you don't what those are, a search like (2) will help. Or ask Quora or even HN. 4) Check the published roadmap. 5) If you want to get even close to the project community, most have an aggregator blog, or an official project blog. E.g. "Planet PHP" etc. There's also frequently mailing lists with links (e.g. Javascript Weekly). You can start reading whatever posts seem interesting to you -- soon you'll have a sense of what the key players are, what developments are coming, etc. 6) Check the relevant Reddit channel for the framework/project/language, or HN for stories on it. The first 4 items don't take more than half a day to go through (of course you could spread them in a weekend or a whole week). The (5) and (6) are more advanced, but still you can dip your toes slowly into them too -- a couple hours per week or so. For more advanced involvement, you can go on irc and say hi to some devs and helpful volunteers. At later stages you can join their dev mailing lists, and even volunteer and help the project yourself.
abritinthebay 11y ago
long story short? There was a fork (called iojs) that moved to using semver and it used v1.0-3.0. It was then merged back into Node (with a ton of great changes to the leadership and development of Node) and the extra changes bumped it to 4.0. But yeah, it's semver so it's more "we've had 3 cycles of major breaking changes" than "it's a completely new product".
watson 11y ago
As others have pointed out, a lot of stuff have happened over a very short period of time. Among the things, Node have a switch to use Semantic Versioning (semver) where the leading version number (major) is bumped every time a breaking change is introduced. The result is that the major version will increase more quickly than we've been used to. If you'd like to read more about semver, check out: http://semver.org http://semver.org
MrZongle2 11y ago
Not sure why you're being downvoted. As others have said, there have been very rapid, recent developments in the node.js world. I think the question is valid, especially for a beginner.
bdcravens 11y ago
That version is from April 2014, and was a full production version behind even before the merger. ("major" releases were even numbered - 0.8, 0.10, 0.12, etc) The current 0.10.x is 0.10.40, which means you were missing out on performance/security fixes. https://nodejs.org/en/download/releases/ https://nodejs.org/en/download/releases/ Also, it's not unusual for project to totally jump versions - a notable example is Rake, which jumped from 0.9 to 10.0.

by cdubzzz 11y ago

Having just started learning about and using node, I read this release note and then this made me say to myself, "What the fuck?" [15:39 user@host ~] > node -v v0.10.25

_RPM 11y ago

Using your distributions package manager you'll get the older versions. I'm guessing you're using Ubuntu? Better off just compiling from source.

dahjelle 11y ago
You can also use nodebrew[1], which also allows you to install multiple versions in parallel. [1] https://github.com/hokaccha/nodebrew https://github.com/hokaccha/nodebrew
- brokentone 11y ago
  I prefer n[1], but others might like nvm[2] which is quite similar to rvm. [1] https://github.com/tj/n https://github.com/tj/n [2] https://github.com/creationix/nvm https://github.com/creationix/nvm

amccloud 11y ago

Node jumped from v0.x to v4.x when iojs merged back into node (something like a month ago)

bdcravens 11y ago
Do note that even before that, node was on 0.12, and 0.10.25 is from April 2014.

coldtea 11y ago

>Having just started learning about and using node, I read this release note and then this made me say to myself, "What the fuck?" If you've started learning node, then it probably makes sense to follow the community portals and news too. In which case you'd known about io.js and the 4.x thing. In other words, get into the whole project / community / culture.

yincrash 11y ago
Not everyone has time to get into an entire community / culture when they just need to use tools.
- bdcravens 11y ago
  I think monitoring the repository for an open source project you depend on is critical. Even if you're not trying to be cutting edge, we have several years of security incidents that tell us that you can't turn a blind eye.
- coldtea 11y ago
  On the contrary. It's when you need to use the tools when you most have to get into the community/culture. If you just wanna learn something as a hobby, have fun, etc, then you don't have to do anything. But knowing about the product, its community and its release roadmap is essential for anything you want to use to put something in production. Actually it's essential for even considering to use this technology over another. And I wont even get into security and stability issues that a closer look at the project will make you aware of sooner.
watson 11y ago
a LOT of stuff have happened in the Node community over a very short period of time. So it's understandable that not everyone have had the resources to follow everything :) Especially if you're just getting started and not using Node full time yet.
elros 11y ago
> In other words, get into the whole project / community / culture. Could you elaborate on that? Which resources do you think would be useful to be followed to get into the culture and community?
- coldtea 11y ago
  1) At the very least, read the projects About Us/History page, and its Wikipedia article, to get a sense where it stands for in the grand scheme of things. 2) Do some searching to see what alternatives exist. Even typing "alternative to Node.js" will give you some starting points. E.g. when you find out about NW.js and want to use it, it would pay to know that there's also Electron. If you learn there's this hot Angular thing, it should pay to also check React and Ember. 3) Also check how "alive" the project is. Things like GitHub followers, latest commits, release frequency, etc, will give you a sense of that. You don't have to go wild with this and (2) -- just check the 2-3 more prevalent projects in your niche. Again, if you don't what those are, a search like (2) will help. Or ask Quora or even HN. 4) Check the published roadmap. 5) If you want to get even close to the project community, most have an aggregator blog, or an official project blog. E.g. "Planet PHP" etc. There's also frequently mailing lists with links (e.g. Javascript Weekly). You can start reading whatever posts seem interesting to you -- soon you'll have a sense of what the key players are, what developments are coming, etc. 6) Check the relevant Reddit channel for the framework/project/language, or HN for stories on it. The first 4 items don't take more than half a day to go through (of course you could spread them in a weekend or a whole week). The (5) and (6) are more advanced, but still you can dip your toes slowly into them too -- a couple hours per week or so. For more advanced involvement, you can go on irc and say hi to some devs and helpful volunteers. At later stages you can join their dev mailing lists, and even volunteer and help the project yourself.

abritinthebay 11y ago

long story short? There was a fork (called iojs) that moved to using semver and it used v1.0-3.0. It was then merged back into Node (with a ton of great changes to the leadership and development of Node) and the extra changes bumped it to 4.0. But yeah, it's semver so it's more "we've had 3 cycles of major breaking changes" than "it's a completely new product".

watson 11y ago

As others have pointed out, a lot of stuff have happened over a very short period of time. Among the things, Node have a switch to use Semantic Versioning (semver) where the leading version number (major) is bumped every time a breaking change is introduced. The result is that the major version will increase more quickly than we've been used to. If you'd like to read more about semver, check out: http://semver.org http://semver.org

MrZongle2 11y ago

Not sure why you're being downvoted. As others have said, there have been very rapid, recent developments in the node.js world. I think the question is valid, especially for a beginner.

bdcravens 11y ago

That version is from April 2014, and was a full production version behind even before the merger. ("major" releases were even numbered - 0.8, 0.10, 0.12, etc) The current 0.10.x is 0.10.40, which means you were missing out on performance/security fixes. https://nodejs.org/en/download/releases/ https://nodejs.org/en/download/releases/ Also, it's not unusual for project to totally jump versions - a notable example is Rake, which jumped from 0.9 to 10.0.