If you won't even consider an article written by the people behind the javascript engine inside node.js, I don't think I can come up with a better/more reliable resource.
You do realise that Avalander has considered said article, right? They are saying two things about it: 1) its conclusions are dubious and 2) it doesn't really address your point or their objection to it. If this doesn't show that they've considered it, I don't know what does.
The point Avalander is contesting is this claim:
Isn't it cleaner and easier to read with async/await?
To which I am afraid I must side with Avalander and say that neither you nor your sources have provided good support for it. async/await reads differently than promises. But that's just it. Not cleaner, nor better, just different.
And I am going to discuss the second source you mention. Particularly the sentence you quoted:
With async functions, the code becomes more succinct, and the control and data flow are a lot easier to follow, despite the fact that the execution is still asynchronous.
I can't help but notice that they write that just below an example where they've rewritten promise syntax to async/await using two fewer lines of code (one of which is merely a )};) and making two other lines twice as long. Specifically, while the promise syntax uses 168 characters, the async/await syntax uses 181. That's 13 extra characters for the supposedly more succint code of async/await. Even if it were 5 characters less, that'd be dubious evidence on which to ground the claim that async/await is more succinct, simply because it's only one example with too small a difference to draw any conclusions.
By the way, I'm not saying that promise syntax is better than async/await. All I'm saying is that I find the claim that async/await is better or clearer wanting.
We concluded earlier than readability is subjective, so I don't think it makes any sense to keep arguing about what you find best.
My point is simply this: We can all have our opinions and preferences but, in the interest of objectiveness, I believe the best we can do is follow reliable sources. Unless you have the time to explore the matter in depth and write your own article with your own conclusions.
Both links I've shared on this thread I consider to be reliable and present async/await as an improvement to writing asynchronous code in javascript. And there are many other sources that explore this statement in depth and conclude the same thing. This article was not meant to list the pros and cons of async/await but merely to share tools that worked for me and that are supported by documentation written by people far more experienced than me in the subject.
Here's another article from this very platform that explores the subject more in depth.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
You do realise that Avalander has considered said article, right? They are saying two things about it: 1) its conclusions are dubious and 2) it doesn't really address your point or their objection to it. If this doesn't show that they've considered it, I don't know what does.
The point Avalander is contesting is this claim:
To which I am afraid I must side with Avalander and say that neither you nor your sources have provided good support for it.
async/awaitreads differently than promises. But that's just it. Not cleaner, nor better, just different.And I am going to discuss the second source you mention. Particularly the sentence you quoted:
I can't help but notice that they write that just below an example where they've rewritten promise syntax to
async/awaitusing two fewer lines of code (one of which is merely a)};) and making two other lines twice as long. Specifically, while the promise syntax uses 168 characters, theasync/awaitsyntax uses 181. That's 13 extra characters for the supposedly more succint code ofasync/await. Even if it were 5 characters less, that'd be dubious evidence on which to ground the claim thatasync/awaitis more succinct, simply because it's only one example with too small a difference to draw any conclusions.By the way, I'm not saying that promise syntax is better than
async/await. All I'm saying is that I find the claim thatasync/awaitis better or clearer wanting.We concluded earlier than readability is subjective, so I don't think it makes any sense to keep arguing about what you find best.
My point is simply this: We can all have our opinions and preferences but, in the interest of objectiveness, I believe the best we can do is follow reliable sources. Unless you have the time to explore the matter in depth and write your own article with your own conclusions.
Both links I've shared on this thread I consider to be reliable and present
async/awaitas an improvement to writing asynchronous code in javascript. And there are many other sources that explore this statement in depth and conclude the same thing. This article was not meant to list the pros and cons of async/await but merely to share tools that worked for me and that are supported by documentation written by people far more experienced than me in the subject.Here's another article from this very platform that explores the subject more in depth.