Promise.prototype.finally ships in Chrome 63! https://developers.google.com/web/updates/2017/10/promise-finally …pic.twitter.com/KY5h3WmRQW
You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
What about Promise.all([promise1, promise2).then(...).catch(...).finally(...)?
Same thing there: I’d prefer `await`ing the result of `Promise.all` combined with try/catch/finally.
What if I need to propagate the error somewhere else? Throw in finally again?
Yes. `finally` returns a promise so you can keep chaining
Whoa. Explain what you found?
It boils down to the fact that `async` and `await` are strictly better than vanilla promises. https://mathiasbynens.be/notes/async-stack-traces …
I haven't read any reason why promise.finally(...) shouldn't be used. Doesn't try{ await promise;} finally{} do the same thing?
That’s the reason. Promise#finally is not that useful given `try { } finally {}` + async/await. Also https://mathiasbynens.be/notes/async-stack-traces …
Wait, what? Why does it ship if it should never be used? :(
I'm guessing that Mathias and the person implementing `Promise.prototype.finally` are not the same.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.