Live data from Hacker News

Error handling in Node.js and Express

itamarweiss.com

21–23 of 23 posts

Re: Error handling in Node.js and Express

#21

Earlier quoted context omitted.

You don't seem to know a lot about node. The whole philosophy is "small modules that do one thing well and get out of the way for the rest". If what you like are big frameworks that handle these kinds of things for you, e.g. Rails, Grails, Django ... Don't pick on Node for not doing something it was not created to do, and will never do.

Node was created to not handle error conditions? How is that defensible in a HTTP server?

Simply put because node is NOT an http server, that's a common misconception

Re: Error handling in Node.js and Express

#22
post #12

Earlier quoted context omitted.

Not at all. Express is more like Rack than Rails. It provides routing and middleware setup... and that's pretty much it. It's a microframework designed to be minimal, so you are crticising its core design. You should compare Rails/Django to full-fledged frameworks such as Geddy/Tower/Locomotive/Meteor/Compound... Many of these frameworks are built on top of Express, leveraging it just like Rails/Sinatra leverage Rack…

So Rack doesn't handle errors properly now? Node.js error handling sucks, period.

Well, you do seem to be an expert ... Error handling works pretty well if you know how to code (we run a seever in production with 2M requests per day on node and we manage errors pretty well)

Re: Error handling in Node.js and Express

#23

Earlier quoted context omitted.

So Rack doesn't handle errors properly now? Node.js error handling sucks, period.

Well, you do seem to be an expert ... Error handling works pretty well if you know how to code (we run a seever in production with 2M requests per day on node and we manage errors pretty well)

I didn't say it is impossible, it just sucks compared to other platforms/languages.
Post reply on HN