-
-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
What about promises instead of callbacks? #17
Comments
As the promises is dropped in node (According to http://howtonode.org/promises) i would prefer the standard way. But if it doesn't cause any overhead (and someone find the time to implement it) I guess we could support both styles :) |
I like promises alot.... using https://github.com/kriskowal/q for example. |
It feels like its trivial to add, I can look in to it later. Regarding that promises were dropped in Node 0.2, so would I have done with that syntax (attaching to events). The Q way of doing it with chainable code is much nicer! |
I would possibly move this to a later milestone and get node style callbacks stabilized first. |
Check :) |
I haven't got time to look in to this now, but more and more ppl are moving towards promises in node as well http://spion.github.io/posts/why-i-am-switching-to-promises.html |
It's no question about doing it or not, if you ask me. |
Removed milestone, it will be implemented when someone submit a pull request :) |
Any thoughts @Hexagon @kmpm ? Can't think of an issue to have both though...
The text was updated successfully, but these errors were encountered: