4 ms·

Quick question: With ES6/ES2015 based native promises on the way (see https://babeljs.io/docs/learn-es2015/ https://babeljs.io/docs/learn-es2015/ ), why would

Quick question: With ES6/ES2015 based native promises on the way (see https://babeljs.io/docs/learn-es2015/ https://babeljs.io/docs/learn-es2015/ ), why would you still want to use something relatively proprietary like Bluebird?

creullin 11y ago
Good reasoning here. Bluebird also has alot of utility methods that native promises don't have/support. http://programmers.stackexchange.com/questions/278778/why-are-native-es6-promises-slower-and-more-memory-intensive-than-bluebird http://programmers.stackexchange.com/questions/278778/why-ar...
deleted 11y ago
[deleted]
hiphipjorge 11y ago
OP here. Bluebird provides a lot of really useful methods and abstractions over promises that we use on a daily basis. Basically all the methods I point out in the article are not part of the Promise spec (and probably won't be). The other thing that Bluebird helps a lot with is providing functionality around transitioning from non-promise code to promises by providing methods such as `promisify`, `promisifyAll`, `fromCallback`, and `asCallback`.
_greim_ 11y ago
Bluebird made a name for itself by really, really focusing on V8-specific optimizations. Also it has added a lot of features that go beyond the promise spec, thus becoming one of those bandwagony swiss army knife sort of libraries. I personally use it for how efficient it is in Node.
Touche 11y ago
"proprietary" is an odd way to describe a MIT licensed project.
onestone 11y ago
Because: 1) Bluebird is orders of magnitude faster and more memory-efficient than the current V8 native promises. Better native promises performance has been promised, but we are still waiting for it. 2) Bluebird is just as much standard-compliant as are the native promises. 3) Bluebird has very useful extensions, which are not (yet?) part of the standard. You are not forced to use them, but they are still very nice to have.
- danesparza 11y ago
  Thanks! I appreciate the points.

creullin 11y ago

Good reasoning here. Bluebird also has alot of utility methods that native promises don't have/support. http://programmers.stackexchange.com/questions/278778/why-are-native-es6-promises-slower-and-more-memory-intensive-than-bluebird http://programmers.stackexchange.com/questions/278778/why-ar...

deleted 11y ago

[deleted]

hiphipjorge 11y ago

OP here. Bluebird provides a lot of really useful methods and abstractions over promises that we use on a daily basis. Basically all the methods I point out in the article are not part of the Promise spec (and probably won't be). The other thing that Bluebird helps a lot with is providing functionality around transitioning from non-promise code to promises by providing methods such as `promisify`, `promisifyAll`, `fromCallback`, and `asCallback`.

_greim_ 11y ago

Bluebird made a name for itself by really, really focusing on V8-specific optimizations. Also it has added a lot of features that go beyond the promise spec, thus becoming one of those bandwagony swiss army knife sort of libraries. I personally use it for how efficient it is in Node.

Touche 11y ago

"proprietary" is an odd way to describe a MIT licensed project.

onestone 11y ago

Because: 1) Bluebird is orders of magnitude faster and more memory-efficient than the current V8 native promises. Better native promises performance has been promised, but we are still waiting for it. 2) Bluebird is just as much standard-compliant as are the native promises. 3) Bluebird has very useful extensions, which are not (yet?) part of the standard. You are not forced to use them, but they are still very nice to have.

danesparza 11y ago
Thanks! I appreciate the points.