Asynchrony: Under the Hood - Shelley Vohr - JSConf EU
ฝัง
- เผยแพร่เมื่อ 26 มิ.ย. 2018
- This talk will explore the conceptual underpinnings of asynchronous programming options, and the drawbacks and advantages to each. JS has supported callbacks since 2009, and as years have gone by it’s added support for promises, generators, and now async/await. On a surface level, each of these techniques seeks to answer a question of how to access data not immediately available, but a deeper look into how each works on a granular level will show their implementation differences and how these differences affect usage. We’ll also take a look at how intermediate values, and errors are affected by each method. I’ll walk through a series of scenarios so you can better visualize performance differences, and how each method propagates data through the stack and the event loop. Finally, I’ll talk about where the future of async may be headed. Armed with new knowledge from this deep dive, the potentially treacherous road to fully understanding async will hopefully become a smoother ride!
OMG JSConf EU is coming back in 2019 2019.jsconf.eu/ - วิทยาศาสตร์และเทคโนโลยี
![[TH] GEN vs SEN | FPX vs TH - VALORANT Champions 2024 DAY 1](http://i.ytimg.com/vi/VcyH-0LAlhs/mqdefault.jpg)
Callbacks, promises, generators, and async/await all explained in 25 minutes. Well done!
It takes so much effort to make something complex, easy to understand. This is a really impressive talk!
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.
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.
Most underrated talk of entire jsconf
In the hell of tutorials, This is the true gem
A very good explanation for promises vs callbacks, thank you!
Truly impressed by this talk. I thought I knew everything about async/await and promises but she proved me wrong.
This is a great talk. Deserves more views!
Thanks @Shelley Vohr! Good job!
Great talk! Everything clearly explained
I wanted to have seen this talk so much earlier. Very well done.
awesome talk, thank you.
Thanks for the awesome lesson.
Excellent Job explaining!
Damn...! this engineer got some serious and rare content on callback, promises and async/await.
Really great talk!
21:00 actually made me go "ohhhhhhhhhh"
Indeed ! The combination of destructuring, async/await and Promise.all() to have a non-blocking version of multiple await is really smart
Thanks! Needed some time to get use to academic style.
yup i had to use notebook to write, but was explained clearly :) :D
probably cause she read it
This was so goood. Great job!
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)
yaa thats right its applicable for async calls only, for sync call it will wait in the call stack.
So that's why callbacks are not guaranteed to be asynchronous. But promises are, even when they are already resolved/rejected.
Awesome ! It would be even more perfect with a mention to Observables though. But congratulation, very clear and sweet to listen to :-D
Nice job. Easy to understand.
pretty much reading "YDKJS: async & performance"
Love the Intro Music
First slide is a meme of Nazaré, a character from a famous tv show here in brazil! LOL
Well executed!! most of the time i ignored error handling, not anymore :)
Great talk
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();
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
Super :)
"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.
Since every callback is asynchronous (eg: setTimeout(cb, 0)), it will execute in the order specified.
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.
you can find the answer here at 27 min th-cam.com/video/cCOL7MC4Pl0/w-d-xo.html.
const loop = () => Promise.resolve(loop); loop();
Every Single time you call dot then on a promise it creates and return a new promise
I aren't yet sure of the role of queues and their scope exactly.
I just watched this prior and is maybe what you are looking for: th-cam.com/video/8aGhZQkoFbQ/w-d-xo.html
good ..
Brazilian meme in the first slide haha
i googled her name and looked at her github and immediately realized i have no fking chance in this field
Inversion of Control doesn't cause significant trust issues.
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.
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.
Have you seen how other male developers dress when they go to other big conferences? Geez. She's totally fine.
Quiero aprender inglés 😪😪😪🥺 para entender mejor.
Y si ya se que TH-cam tiene subtitulos gracias
Her expertise on this shit is srsly turning me on 😂