Node v0.5.0 just released

#1

Post by tonyskn » Wed, Jul 06, 2011, 6:22 AM UTC

Node v0.5.0 just released
blog.nodejs.org

Re: Node v0.5.0 just released

#2

Post by steilpass » Wed, Jul 06, 2011, 7:48 AM UTC

As a note: v0.5.0 is unstable. So just switch for hacking & testing not for your running applications.

Re: Node v0.5.0 just released

#3

Post by DrJ » Wed, Jul 06, 2011, 8:24 AM UTC

- add child_process.fork

- add os.getNetworkInterfaces()

- add remoteAddress and remotePort for client TCP connections

I've been waiting for them to push these features out. (yes, I know you already have the address & port if you are a client).

Re: Node v0.5.0 just released

#4

Post by secoif » Wed, Jul 06, 2011, 8:53 AM UTC

I have never seen so much emphasis on the 'unstable' aspect of a software release.

eg http://twitter.com/#!/search/nodejs%20unstable

Though I know about the even/odd thing, it seems rather damaging to the platform to be announcing 'unstable' seemingly 'major' releases, don't you think? Why not Alpha? or Beta? or some other common convention? Ugh.

Re: Node v0.5.0 just released

#5

Post by rjrodger » Wed, Jul 06, 2011, 9:20 AM UTC

secoif wrote: post #4

I have never seen so much emphasis on the 'unstable' aspect of a software release. eg http://twitter.com/#!/search/nodejs%20unstable Though I know about the even/odd thing, it seems rather damaging to the platform to be announcing 'unstable' seemingly 'major' releases, don't you think? Why not Alpha? or Beta? or some other common convention? Ugh.

This is not a desktop app. The versioning requirements are different.

Many server systems use this convention as a way of embedding an extra bit of info (stable/unstable) for sys admins.

Many people are using Node to push boundaries in various ways, so they are using the unstable versions. I did this with 0.3, but 0.4 is good enough for the moment.

Re: Node v0.5.0 just released

#6

Post by robinduckett » Wed, Jul 06, 2011, 9:31 AM UTC

I would love it if they started adding support for JS1.7 / JS1.8 :(

Re: Node v0.5.0 just released

#7

Post by tedsuo » Wed, Jul 06, 2011, 9:32 AM UTC

secoif wrote: post #4

I have never seen so much emphasis on the 'unstable' aspect of a software release. eg http://twitter.com/#!/search/nodejs%20unstable Though I know about the even/odd thing, it seems rather damaging to the platform to be announcing 'unstable' seemingly 'major' releases, don't you think? Why not Alpha? or Beta? or some other common convention? Ugh.

As you noted, even is the stable/production version and odd is unstable/development version. The goal is to get a number of changes in at once so that you can have a stable branch that's around for a decent amount of time. If you are making multiple changes before releasing a stable branch, how would you describe them? If they get libuv working properly, is that then from alpha to beta since it is now more stable? What if they then rewrite http.request and experiment with different APIs; is it still beta even though it is probably more unstable than the last release? Why not simply version the dev branch with every release, note the changes, and avoid the semantics?

Re: Node v0.5.0 just released

#8

Post by tedsuo » Wed, Jul 06, 2011, 9:43 AM UTC

robinduckett wrote: post #6

I would love it if they started adding support for JS1.7 / JS1.8 :(

They must wait for v8 to support it.

Re: Node v0.5.0 just released

#9

Post by 8___D » Wed, Jul 06, 2011, 10:06 AM UTC

DrJ wrote: post #3

- add child_process.fork - add os.getNetworkInterfaces() - add remoteAddress and remotePort for client TCP connections I've been waiting for them to push these features out. (yes, I know you already have the address & port if you are a client).

I got too excited about child_process.fork before I read the description. I was imagining it would be like C where I can fork, setup the env and exec. That would probably be tricky and very ugly to implement, though..

Re: Node v0.5.0 just released

#10

Post by whatwhatwhat » Wed, Jul 06, 2011, 10:58 AM UTC

8___D wrote: post #9

DrJ wrote: post #3

- add child_process.fork - add os.getNetworkInterfaces() - add remoteAddress and remotePort for client TCP connections I've been waiting for them to push these features out. (yes, I know you already have the address & port if you are a client).

I got too excited about child_process.fork before I read the description. I was imagining it would be like C where I can fork, setup the env and exec. That would probably be tricky and very ugly to implement, though..

I don't think it would be too many lines of code, tbh http://nodejs.org/docs/v0.5.0/api/all.html#child_process.exe...