Asynchrony: Under the Hood - Shelley Vohr - JSConf EU

[@bagoquarks]

Callbacks, promises, generators, and async/await all explained in 25 minutes. Well done!

[@Dygear]

It takes so much effort to make something complex, easy to understand. This is a really impressive talk!

[@paulalexwilson]

Truly understanding something requires that we have a solid appreciation of at least 1 abstraction deeper. This talk was exactly what I was looking for.

[@pixelpaxal]

If you already have a good grasp of callbacks, promises and async/await in javascript, this talk is a good review to put these these things into perspective and language evolution context, it could help one understand when to use one over the other.

[@sandeepparmar3113]

In the hell of tutorials, This is the true gem

[@toxicdesire8811]

Most underrated talk of entire jsconf

[@AccelerateEffectively]

Truly impressed by this talk. I thought I knew everything about async/await and promises but she proved me wrong.

[@nztuber]

Great stuff! At 5:38 to be clear, the execution order suggested on the right is not true for *all* callbacks, only *asynchronous* callbacks. (If they are synchronous callbacks then the invocation order would be doA, doB, doC, doD, doE, doF)

[@rtech8779]

yaa thats right its applicable for async calls only, for sync call it will wait in the call stack.

[@yuansizhu6271]

So that's why callbacks are not guaranteed to be asynchronous. But promises are, even when they are already resolved/rejected.

[@PiyushAggarwal-hz9es]

6:38 She casually says, "assuming these functions are async". I don't know what that even means in this context.

[@makhdv]

Thanks! Needed some time to get use to academic style.

[@sijanshrestha7278]

yup i had to use notebook to write, but was explained clearly :) :D

[@sKopheK]

probably cause she read it

[@ITWorx]

A very good explanation for promises vs callbacks, thank you!

[@payphones]

21:00 actually made me go "ohhhhhhhhhh"

[@alexagna]

Indeed ! The combination of destructuring, async/await and Promise.all() to have a non-blocking version of multiple await is really smart

[@mojojojo1211]

This is a great talk. Deserves more views!

[@abhikumar2469]

Damn...! this engineer got some serious and rare content on callback, promises and async/await.

[@Henrique-yw1rb]

First slide is a meme of Nazaré, a character from a famous tv show here in brazil! LOL

[@dixztube]

This was so goood. Great job!

[@hkjpotato]

good summary of you dont know JS 1. now. and then, run to complete, continuation, trust. Exception is sync? 2. yield control to event loop? 3. promise is microtask queue, a placeholder of a future status 4. before anyelse can happen

[@ahmedal-obaidi792]

pretty much reading "YDKJS: async & performance"

[@alabidavid4674]

Generators could have an end. That's property done set to true in which case they stop yield anything but done:true. Also, you can terminate generators by return();

[@sanderd17]

I wanted to have seen this talk so much earlier. Very well done.

[@maltegb]

Great talk! Everything clearly explained

[@josephlee5829]

Excellent Job explaining!

[@randy4ii411]

Thanks for the awesome lesson.

[@ssougnez]

Awesome ! It would be even more perfect with a mention to Observables though. But congratulation, very clear and sweet to listen to :-D

[@arunas1]

Thanks @Shelley Vohr! Good job!

[@floopy312]

13:21 Can somebody write me a piece of code with an "infinite microtask loop" like she mentions, I'm not sure how you can do that.

[@monolizm]

you can find the answer here at 27 min kzbin.info/www/bejne/mXSyfWqDeJmDopI.

[@romankos3283]

const loop = () => Promise.resolve(loop); loop();

[@vscode4232]

Great talk

[@asianfoodie5908]

Well executed!! most of the time i ignored error handling, not anymore :)

[@singingofstars]

Nice job. Easy to understand.

[@Mostafaabobakr7]

Love the Intro Music

[@enzoscardamaglia9565]

"Since they're not running in the top-down sequential order you might expect." at 05:57. Has anyone tried that out? If I'm not mistaken in Node, FF, Chrome and Edge the functions run exactly in the sequential order I'm expecting.

[@electroaddiction]

Since every callback is asynchronous (eg: setTimeout(cb, 0)), it will execute in the order specified.

[@kps2642]

awesome talk, thank you.

[@jameswon5497]

Really great talk!

[@HarshitSharma-cd4tr]

Every Single time you call dot then on a promise it creates and return a new promise

[@biboswanroy6699]

I aren't yet sure of the role of queues and their scope exactly.

[@terranova3941]

I just watched this prior and is maybe what you are looking for: kzbin.info/www/bejne/bpKqmY2HoNR5mLM

[@anastazjawrobel8040]

Super :)

[@dumbfailurekms]

i googled her name and looked at her github and immediately realized i have no fking chance in this field

[@giullianopaz8262]

Brazilian meme in the first slide haha

[@BinaryReader]

Inversion of Control doesn't cause significant trust issues.

[@halakhita_hk]

good ..

[@ElChitarrino]

Really great stuff there, thanks a lot! However, I feel the urge to mention it's quite hard to follow due to your verbal breaks each 3-5 syllables. No offense intended.

[@nischalofchrist]

great lesson, learnt a lot, but she should really evaluate how to dress when you are invited to be a speaker in such a huge event.

[@kazmonroy]

Have you seen how other male developers dress when they go to other big conferences? Geez. She's totally fine.

[@philliplam2704]

Her expertise on this shit is srsly turning me on 😂

[@felipepino834]

Quiero aprender inglés 😪😪😪🥺 para entender mejor. Y si ya se que KZbin tiene subtitulos gracias

[@tauiin]

Did it help :P