-
-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
Investigate bluebird for promises #1742
Comments
+1 for this |
👎 prefer native promises - #1699 |
@refack why? They're slower and don't do unhandled rejection detection which is one of the most important features of Bluebird, they also provide worse stack traces. Using Bluebird would mean deleting code and removing cruft, you can remove all the promise code from there and simply do |
@benjamingr, native, because their native. They will become the standard (and improve in performance I'm sure). |
+1 for Bluebird |
Any update on this? Bluebird does seem like the best solution out there currently. |
+1 for Bluebird |
Also Bluebird have fast cute opportunity to use callback on promise: nodeify
After that we will be able to call save so:
and so (classic):
|
@petkaantonov - I recall an argument about |
yes it always returns the promise |
+1 ooooya. |
See #2688 |
Bluebird seems to have the strongest performance benchmarks for promises and seems to match the coming DOM Promises in V8 the closest. I'm wondering if it is a good choice for the interim as a Promises/A+ implementation.
The text was updated successfully, but these errors were encountered: