Promises have just gotten nicer! (withResolvers)

[@RyanThickett]

Honestly I just find the async await pattern so much cleaner anyway, stringing together .then().catch().error() etc... always looked super ugly to me, whereas having a function you can just await and then deal with however you want to after is clean.

[@adolfomartin5456]

I agree with you. Sometimes we have to use new Promise ... but in at the moment I'm sure I've forgotten this video.

[@SoftwareDeveloperDiaries]

I also agree, async await is always better :)

[@sirajabbas5372]

For me also async await is much cleaner and readable. However this is handly where the situations we forced to use promises.

[@chris94kennedy]

pretty cool, some nice sugar. Also prevents the antipattern of an async anon function in a Promise constructor

[@sergiyrudenko905]

Thank you!

[@axel_huth]

👍😎👍

Awesome

[@harrypotil860]

You promised that you would make a vedio on how Discord would have avoided Cassandra beforehand

[@mimshins]

Why not just return Promise.resolve(data) or Promise.reject(error)?

[@sergeyagronov9650]

great video :)

[@SoftwareDeveloperDiaries]

Thanks! 🙏

[@Finn-jp6pn]

Can't we always use async keyword to implicitly return a promise instead of explicitly returning a new promise? 🤔