Probably my answer was a bit harsh. I would argue that most problems are simple enough to solve them using callbacks nicely. Also I would say that using a pattern and liking a pattern are two different issues. But the concept of abstracting the callbacks away using a more composable and more natural way is definitely a good thing, at least in my opinion. The callbacks are a implementation detail of asynchronous io but low-level stuff is not what a normal developer should rely on. Nodes key feature is that it strongly encourages thinking about concurrency but the best concurrency abstraction is the abstraction which abstracts concurrency totally away. All I'm saying is that the node library could evolve when the language does.
-- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
