Discussion on: Why to use async & await instead of the Promise class?

View post

Replies for: I agree that in this case, there's no need for async/await, but whenenver you have logic that needs to happen between the async requests, it makes ...

I'm not a async await hater, for me they are isomorphic which can transform to each other. I even like to mix using promise and async await.

The main problem of this article is the examples to judge async await is better than promise is pretty bad one.

Also, why is no one ever bothered by having to add that try/catch block... I don't understand. I hate it.

Yes, catch is much more elegant.

Can you explain why there must be a try/catch block?

@Manuele J Sarfatti

In a classic promise you have:

const request = somePromise()
  .then(data => doSomethingWithData(data))
  .catch(error => doSomethingWithError(error))

If you switch to using await and you do:

const data = await somePromise()
doSomethingWithData(data)

but the promise fails (throws an exception), then you have yourself an unhandled exception, and the browser will most probably crash your app.

The equivalent of the classic promise is therefore:

try {
  const data = await somePromise()
  doSomethingWithData(data)
} catch (error) {
  doSomethingWithError(error)
}

PS: this is pseudo-code off the top of my head and most probably not working, it's just to give an idea