JavaScript’s Async / Await Compared to Promises with NodeJS

Let's take a look at why async/await blows promises away!

[elkyu]

Pretty good and neat explanation. Liked the points where you show the odd situations & how to handle them in a clean way!

[sweeball]

Thanks! You have shed light on an advanced javascript topic that I am trying to learn. It now makes a bit more sense. Cheers.

[kenkrueger]

Great work! The thing I find odd (from a Java perspective) is how Java is trying to become more asynchronous / less blocking / more like Javascript / Node with Promises and Reactive - at the expense of hard to read code. At the same time JavaScript async/await is moving in the opposite way, seeking the sanity of synchronous processing to dramatically increase clarity.

[bugeera]

hey, which video recorder / editor did you use for this video ?

[sly]

"fetch" doesn't have to be async, and you don't need the promise constructor:
fetch = () => Promise.resolve({ text: "" });

[GifCoDigital]

What was with the quotes around "kind of async" promises ARE async there not kind of async.

[luillyfe]

I know live coding is really hard to do. But in some point the explanation turns out very difficult to follow. I hope you can make another video about this topic.

[johnmartin]

it works perfectly fine if you don't put async keywork in fetch function.

[spencerdavies]

you are awesome! thanks for your videos! keep it up!

[koronci]

nice video..maybe a little preparation ahead wouldn't hurt :)

[LavotiJoelVinayKumar]

The tutorial itself is async and await