Why I think Node.JS is a terrible platform

Re:Why I think Node.JS is a terrible platform by peeters on Sunday September 09, 2012 @03:14AM (#4495192)

I've never jumped on the Node bandwagon either, because I detest Javascript, but...Shouldn't async-style programming be fairly familiar to Javascript developers? At least those who have ever made an AJAX app?

It seems like it was a paradigm shift for the author, but I wonder if it actually is for most people who Node is primarily targeted towards: those who like and regularly use Javascript.

[ Parent | on HN ]

Re:Why I think Node.JS is a terrible platform by hasenj on Sunday September 09, 2012 @05:25AM (#4495390)

I'm actually quite familiar with JS and comfortable with writing callbacks on the client. It's very different from doing server and backend code.

On the client, you don't make too many calls to the server, and if you do, I'd consider that you're doing something wrong.

What I mean is, on the client side, if you need to make 10 calls to the server before you can display something, you're obviously doing it wrong.

So you can avoid a callback mess by simply making sane design decisions.

But on the server side, you have to make several calls to the DB, and thus, the callback hell is unavoidable.

[ Parent | on HN ]

Re:Why I think Node.JS is a terrible platform by nailer on Sunday September 09, 2012 @03:06PM (#4496612)

On the client you have callbacks every time an object has an event handler. It's not just AJAX. And yes, anyone familiar with client side JS should understand and be using callbacks everywhere.

[ Parent | on HN ]

Re:Why I think Node.JS is a terrible platform by hasenj on Sunday September 09, 2012 @06:53PM (#4497339)

Using callbacks to handle user generated event is VERY different from using callbacks inside what should be normal linear control flow.

[ Parent | on HN ]