Live data from Hacker News

Node.js v0.8.0 [stable] is out

blog.nodejs.org

21–30 of 60 posts

Re: Node.js v0.8.0 [stable] is out

#21
post #9
post #7

This looks incredible. Congrats to node core on this milestone! I really appreciate how laser-focused you guys are on code consistency across the board. Looking forward to trying out the cluster and domain modules in strata!

The domain module looks fantastic: http://nodejs.org/api/domain.html "Domains provide a way to handle multiple different IO operations as a single group. If any of the event emitters or callbacks registered to a domain emit an error event, or throw an error, then the domain object will be notified, rather than losing the context of the error in the process.on('uncaughtException') handler, or causing the program to ex…

Thanks! It is marked experimental, and we really do mean that. The API won't change in 0.8, but it probably will change somewhat in the next stable release. Please try it out and let us know what you think, especially in what ways it is lacking, how it actually helps or hurts in real apps, etc.

Re: Node.js v0.8.0 [stable] is out

#22
post #14

Coincidentally, today is the day that I started looking into learning node. Anyone know some good guides which don't use deprecated code?

Shameless self plug: http://danielnill.com/blog/nodejs-tutorial-with-socketio/

Not a full tutorial, but hopefully a decent intro for those looking to learn the ropes.(I would love to hear feedback good or bad)

Re: Node.js v0.8.0 [stable] is out

#23
post #14

Coincidentally, today is the day that I started looking into learning node. Anyone know some good guides which don't use deprecated code?

Oh, and of course, if you don't mind paying for a video tutorial, the latest Peepcode screencasts look promising:

https://peepcode.com/products/full-stack-nodejs-i

https://peepcode.com/products/full-stack-nodejs-ii

(Don't purchase the old ones. They're desperately outdated. These two were published recently and use the latest APIs.)

Re: Node.js v0.8.0 [stable] is out

#24

Earlier quoted context omitted.

I can't believe you managed to get this submitted to HN before I did. That's what I get for posting it to twitter before coming here ;D Since I knew the URL, I could have totally cheated and done it before even uploading the blog post.

Was there a prize for the first person that posted this?

You're probably missing some necessary context here: Isaac is the maintainer of Node.js. So the funny thing is that pooriaazimi was so excited to post this to Hacker News that he beat the project's own maintainer to the punch.

Re: Node.js v0.8.0 [stable] is out

#25

:-D I actually set an alarm this afternoon to submit v0.8.0 as soon as it comes out, if you can possibly believe it ( I still can't believe I've done such a low, degenerate thing and am a little ashamed of myself )! But I'm incredibly happy about this release, specially about the 'new' cluster API[1] that has made my life a whole lot easier! So apologies for being a karma whore, but I was so glad I couldn't resist, i…

I can't believe you managed to get this submitted to HN before I did. That's what I get for posting it to twitter before coming here ;D Since I knew the URL, I could have totally cheated and done it before even uploading the blog post.

Now, quickly release 0.8.1 and make sure you beat everyone ;)

Joke aside, thanks for the great new release. I'm running 0.6 in production sometimes with 3000+ connected users and will soon need to scale. Being able to do so just by upgrading to 0.8 will make my life easier... until many more users come, of course.

Re: Node.js v0.8.0 [stable] is out

#27
post #9
post #7

This looks incredible. Congrats to node core on this milestone! I really appreciate how laser-focused you guys are on code consistency across the board. Looking forward to trying out the cluster and domain modules in strata!

The domain module looks fantastic: http://nodejs.org/api/domain.html "Domains provide a way to handle multiple different IO operations as a single group. If any of the event emitters or callbacks registered to a domain emit an error event, or throw an error, then the domain object will be notified, rather than losing the context of the error in the process.on('uncaughtException') handler, or causing the program to ex…

I've been reading back and forth between this post and the docs and I'm still not really getting it.

Is this just a way of registering a single callback to respond to error events that could be emitted by different operations? What are some examples when this would be better than handling error events individually?

Is it sort of like a try/catch for error events?

Re: Node.js v0.8.0 [stable] is out

#28
post #14

Coincidentally, today is the day that I started looking into learning node. Anyone know some good guides which don't use deprecated code?

It's been a long since I watched "Introduction to Node.js with Ryan Dahl"[1], but although I think it was circa v0.4.0, it's not really outdated. It's a short talk, but it talks a little about Node's philosophy and I highly recommend watching it. I haven't watched Pedro Teixeira's tutorials[2], but many recommend it. But I personally think Manuel Kiessling's online book[3] is the best. It really teaches you to think…

I just started teaching myself node a couple days ago and just finished with Manuel Kiessling's online book yesterday. It really is a great tutorial and helped me a lot. Thanks for the other links, I'm going to check out nodetuts.com later today.

Re: Node.js v0.8.0 [stable] is out

#29
post #14

Coincidentally, today is the day that I started looking into learning node. Anyone know some good guides which don't use deprecated code?

Tekpub has a course on node, it's fairly recent (I think it has been around for 3 months, give or take). The Tekpub site was rebuilt in node as well and the videos talk a little bit about somethings Rob Connery encountered during the process. The series taught me a lot, but my only other exposure was the peepcode video.

http://tekpub.com/view/node/1

Re: Node.js v0.8.0 [stable] is out

#30
post #9

Earlier quoted context omitted.

The domain module looks fantastic: http://nodejs.org/api/domain.html "Domains provide a way to handle multiple different IO operations as a single group. If any of the event emitters or callbacks registered to a domain emit an error event, or throw an error, then the domain object will be notified, rather than losing the context of the error in the process.on('uncaughtException') handler, or causing the program to ex…

I've been reading back and forth between this post and the docs and I'm still not really getting it. Is this just a way of registering a single callback to respond to error events that could be emitted by different operations? What are some examples when this would be better than handling error events individually? Is it sort of like a try/catch for error events?

> Is it sort of like a try/catch for error events?

Yes, but it's also sort of like a try/catch for thrown errors.

    d = domain.create()
    d.on('error', function(e) {
      console.error('an error: ', e)
    });
    d.run(function() {
      throw new Error("whoops")
    })
would console.log, rather than crashing the program.

When an EventEmitter is bound to a domain, their error events and any errors thrown while emitting an event on them will be handled by the domain object that they're bound to.

Post reply on HN