delay VS Bluebird

Manually creating a Promise can look challenging, but you don't have to do that if you stick to async/await and Promise-based APIs. For example, you can use the npm package delay for a promisified version of setTimeout.

`git log --graph --decorate --oneline` is specific to a branch of a repository. Github Network shows the relationship between forks. It is similar but really the question answered by it is "what and where is the work being done" and "what is the relationship between work being done and this repository I'm looking at". It sucks that Network is buried, I think it should be much more accessible.

Eg https://github.com/sindresorhus/delay/network tells me that this work is being maintained actively, but most forks are not merging back. Another one might tell me work on the main fork is stalled, and many users are now doing PRs against a fork of the original.

To make sure last action is ended before doing another one, I add some delay between actions using delay.

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.