Using async generators to stream data in JavaScript 

That "pageIndex = pageIndex +1" line made me vomit a little lol

One of my favorite videos so far! This whole iterators and generators series has been extremely useful to me

Really hyped about higher order async iterables!

Thanks Mattias Petter. I learned a lot. At the end of the journey you take us on, I gazed with amazement at the sleekness of the final async generator code. Like getting to the top of a mountain, completely relaxed while we take in the wonderful view of infinity around us (infinite cat images!)

Where I am in the bootcamp I am attending these videos are very valuable to me! Can't wait for higher order async iterables!

I like to think of the need for iterators as the freedon from the code structure, to peek a "register" whenever I want it: In a loop, your actions are constraint to what you can do between the control line (for/while/do/etc.) and the end of the cycle, while an iterator can be use at any moment in your whole app, and treat each element of the data set in a very free dynamic way.

Best iterator/generator explanations in the Internet. Thanks!

4:13 that sound is killing me :D Thanks, awesome video. What about video around Proxy?

Good Monday morning! Great video! genuinely enjoying this series and looking forward to higher order async generators. Pretty much opened up my youtube channel to leave this comment.

Awesome vid! I am going to go back and re watch the ramp up vids for this to get more out of it. Really cool to watch a full process! thanks!

Please do a video on the stream implications you mentioned at the end

Mpj. I can't thank you enough fir teaching me async generators

What's with the `function flickrTagSearch(tag, page)` defined inside the `function flickrTagSearch(tag)`?

Hey MPJ great video as always! can you do a vdo on socket io in-depth, please? pls show an example on nodejs! :)

hmm, not sure if we can _replace_ rxjs/bacon/etc. with async iterators, becuase Rx streams are push-based and the streams you defined (async iterators) are pull-based. The nature is different. The difference is in who holds the control flow. In pull-based, the owner of the iterator controls how many items can be consumed (how many cat pictures can you see in a period of time in order to get satiscaftion), whereas in push-based the stream is an observable, so flow is inverted (IoC), the platform/lib controls it and invokes the subcriber automatically (the cat pictures change depending on the device and its settings). Both are iterators and both are async, they just differ in who holds the control: you (then it's good that you HAVE it under control), or the platform (IoC, then it's good that you DON'T HAVE to have control) ;) In order to actually _replace_ RxJS with async iterators, you'd have to (1) re-implement all operators (just as rx did), (2) implement observable/observer pattern (just as rx did) so that the stream is lazy as long as nobody subscribed to it. So although you do have the low-level primitives in your hands, you'd have to reimplement the missing higher-level traits.

Hi Mpj! I work with nodejs, where the concept of streams is already integrated into the language. Since an async generator expresses the concept of streams, does make sense to use it in nodejs since the streams already exists? If yes, when? Congratulations for the videos!

OMG, it seem so powerful in so few lines. \o/ Yatsa!

Great series! Thank you!!

Good Monday Morning :)

Video suggestion: Proxy object in JavaScript, Vue 3 implementing his new engine with Proxies and IE slowly diyng will boost the usage of this feature.

Really cool channel! Thank you, thank you, thank you :)

Hey MPJ! Currently I'm translating subtitles of this video to Russian and on 0:40 you said "for loop provide iterator"? Am I right? If it's true, that's actually not correct, for loop do not have and cannot have iterator, but its using iterator in order to iterate over collection's items.

amazing video ! thanks !

By the way, all readable streams in Node.js 10 are async iterators! So we can: for await (let c of fs.createReadStream(filename) { console.log(c) } see: twitter.com/mikeal/status/993925507967205378

A thing close to infinity 5:55 the JavaScript infinity or the mathematical infinity ?

What is the editor/plugin that you use for writing the js code and getting a function result next to the line where it's executed?

just try to add some cache to show the image when fully loaded, the flickering from flickr hurts my eyes XD for await(const url of cats) { const cache = new Image() const img = new Image(150, 150) cache.src = url cache.onload = () => img.src = cache.src yield img }

Diggin' the Moderat.

Mattias you are a fucking genius!

why i got this result? {stat: "fail", code: 100, message: "Invalid API Key (Key not found)"}

nice videos, thank you) what about continuing "Top 8 developer habits" series?

Awesome stuff. Is it possible to use Async Generator with angular data tables. If No, What would be the alternative way to do it.

23:10 Maybe you could do yield* pageData

MPJ's avatar looks like RDJ XD

in what cases in your past, would you liked to use this streams iterators?

I'm not really understanding how using iterators differs from using arrays in a stream like you explained, if you created an iterator that is iterating over an array/cache. Thanks, great work btw

It looks a lot like Python's iterators / generators (yield) and asyncio (await).

Am I the only one who does not understand how this `photoindex++ / cache[photoindex] / photoindex=0` thing works?

I wonder if someone recognized his cat in the video. lol

am i alone who think that he looks like tony starck?

You are a genius ... When I get $$$ I will become a patron. In the meantime please accept my rainbows and unicorns🌈🦄

Now async generators make sense and seem super useful. Before, they where just a new useless feature

The `Code from the episode` link 404's :(

I missed something or you removed your genious intro? :)

can we talk about this wall light? whats going on with Swedens, where did you get this? I want one and become a youtuber :D

To bad you didn't show how to delegate the paging (inner loop) to another async generator with yield* ;-)

Why explaining simple things so very comlicated and time consuming? explaination in 1 minute: async function* generator(counter: number) { while(counter < 5 ) { yield await (await fetch(`jsonplaceholder.typicode.com/posts/${counter}`)).json() counter++ } } const gen = generator(1) for await (const item of gen) { console.log(item) } keep the examples short, brief and compact. just my opinion..