Notice
There are no need for additional +1 or pretty pleases. @ljharb is already working on it, and all you are doing by +1'ing is spamming a whole bunch of people.
Further more, it has been mentioned that no contributions are required at this time for the implementation of this feature.
So let's all keep quiet for a while, and give a chance to @ljharb to finish his work :)
I know it is very early to start the conversation on this matter, but with a potential first release by IO.js coming up in little over a month, I thought it might be an interesting conversation to have.
At this point, NVM manages, well, Node.js versions. However, nodejs/node#28 already started to discuss ideas like aliasing node and so on. I would be against that idea in general, but in the context of NVM, it might just make sense: after all, you explicitly pick a node version, and are told about the one you will want to use.
Anyway, the core idea is: if we are to see node forks, how about managing them too?
nvm install node/v0.10.33
nvm install iojs/v1.0.0-alpha
nvm install hypotheticalnode/v1.2.3
Doing so - and again, perhaps auto-alias commands? - could make it very nice for developers; keep the same old habits, just change your node version.
TBH I am not sure if it's that good of an idea in the first place, but it's probably one that ought to be interesting to discuss.
Notice
There are no need for additional +1 or pretty pleases. @ljharb is already working on it, and all you are doing by +1'ing is spamming a whole bunch of people.
Further more, it has been mentioned that no contributions are required at this time for the implementation of this feature.
So let's all keep quiet for a while, and give a chance to @ljharb to finish his work :)
I know it is very early to start the conversation on this matter, but with a potential first release by IO.js coming up in little over a month, I thought it might be an interesting conversation to have.
At this point, NVM manages, well, Node.js versions. However, nodejs/node#28 already started to discuss ideas like aliasing
nodeand so on. I would be against that idea in general, but in the context of NVM, it might just make sense: after all, you explicitly pick a node version, and are told about the one you will want to use.Anyway, the core idea is: if we are to see node forks, how about managing them too?
Doing so - and again, perhaps auto-alias commands? - could make it very nice for developers; keep the same old habits, just change your node version.
TBH I am not sure if it's that good of an idea in the first place, but it's probably one that ought to be interesting to discuss.