Bluebird VS es6-cheatsheet

It might, if the code can be optimized. There are all sorts of reasons why it might not. For example, at one point in time, a switch statement with more than 128 cases could not be optimized.

https://github.com/petkaantonov/bluebird/wiki/Optimization-k...

Prior to ES6, we used bluebird or Q. Now we have Promises natively:

For example: https://github.com/petkaantonov/bluebird/wiki/Optimization-killers

The standard library is quite barebones so you’ll need to import something else (Think bluebird for JS). You need an executor to run a future. I recommend using https://github.com/tokio-rs/tokio and reading their documentation.

I had a look at the bluebird promise FAQ, in which it mentions that .then(success, fail) is an antipattern. I don't quite understand its explanation as for the try and catch.What's wrong with the following?

I have not looked into how packages like bluebird does this, but I expect it is similar to the above items I expressed

You can look at the implementation of Bluebird an implementation of Promises that preceded them being available in JS itself.

This is about 6 years late. Also noticed it was a direct copy of https://github.com/DrkSephy/es6-cheatsheet (which was written 7 years ago)

es6-cheatsheet https://github.com/DrkSephy/es6-cheatsheet