Re: Node and callback hell

Kevin,

Yes, we may be talking about different things. I don't believe I ever used
the term "callback hell", though I have read references to it. Just so that
we're on the same page, could you describe the problem?

I can imagine problems occurring when "registering" call-backs from say
"nested" routines if you don't implement some mechanism such as a "queue"
to ensure that the I/O and call-back are performed synchronously.
Subsequent I/O requests may depend on an initial request completing
successfully.

I followed your GitHub link. But I always have a hard time looking at
source-code projects without adequate background or explanation of the
project. References to GitHub typically come across as uber-geeky. Like,
Hello Visitor Dude... don't you just get it?

I don't really understand "promises". So, no I would neither reject nor
endorse it until I understand it.