I thought this will be pointless, like most things in JS, but it actually does make some sense

Thanks! I've been watching primagen's game development videos and had the insane desire to start learning vim by building an ASCII game for my kids. This video was a perfect kick start to the project.

Really cool! I like to know this :D

Good video nice job bro

DILF is also a compliment to middle aged men! dootodoo!

유튜브 로고가 한글 같네요 텀

Font Name?

What was that ending?

Doing God's work, loved the explanation and how simple it was to understand

literally can't see your keystrokes on the keyboard taking up 1/4 of your screen.

10/10 ending absolute nonsense

What happens if the server returning the body goes down while providing the response body byte by byte?

I like \033[31m because it makes it spooky red.

This is awesome mate!

Thanks for the amazing and informative video. Makes me want to explore everything that comes like lazy more!

Tom, could you share your vim config? :)

amazing, simple and easy to understand about stream

Beautiful!

probably because response is just connection response without data. Then you need to wait again while data is being streaming in binary, and then it does the parse. ok, boring. I wrote the guess after watching 30 sec, and yeah, that what it is.

The browser and server already do the heavy lifting of streaming and parsing the big piece of data in small chunks, incrementally (thus the 'streaming'). So in the frontend, all you need to do is create a 'for of' loop (because it can 'await' things) and build a string/content with the coming data. I've been doing this for years because I have many circumstances where we had to display things as they come in, rather than waiting for the whole thing to process and then BANG, fill up the screen. It's a nice, informative/educational piece of video nonetheless. Well done!

Fetch only resolves the header? So the Response is not a response. It's more like a handshake.

make a JavaScript playlist

Use then, and no need of second await.

In HTTP, we have a Content-Length header that indicates the number of bytes in the response body. Given that the await in the first fetch operation retrieves only the headers, does this imply that the Content-Length header cannot be set correctly before the entire body is streamed?

Now can you do this during a technical interview.

This is first explanation which make me understand that. Thank you!

Maybe wrap it into fatchJson with one visible await

Such a nice video. Very beautiful style and clear explanation! ❤

help me i am alive

Lifting one of the greatest mysteries ever.

I like the simple explanation and the overall vibes.

Should I await before I subscribe?

Hey, that is a great explanation. I understood that the complete response body is waiting to get a transfer, but I was wondering when the response body converted into valid JSON. I know that conversion takes sometime incase of a huge pay load.

RegSys you gotta pay for this !!!

fetch() is poorly named

You don't see too happy about Regsys..? With 51% of your youtube channel. What did you do??

Let's try to bring this into production, it's so fast ;P

maybe can explain it better from tcp perscpective

Ooooh, it’s an ad slot

the video at the end is cut by those cyber bots

never saw anyone get so sad with being sponsored, blink twice bro if you need help.

this may be framework-specific, but can you return an un-awaited response.json()?

You using deno 2.0

Very interesting stuff and I never thought about it, but it seems to be pretty easy to modify the prompts. Thanks for looking at the stuff! :) However, I do not get the sponsored part. What does it mean? Is it a joke, will the content of the channel change? Are you enslaved now? What does it mean?

Hey man, love ur vids. Thanks. Tho that regsys part sounded kinda sad

interesting

Nice stuff! Ofcourse, as a Go programmer, I don't deal nor look too deep into JS, this was still useful and nicely illustrated. Give us more!

Great video, thanks! Side question, can you tell me what font are you using it look really well spaced and clear to read, thanks :)

Very interesting

Great presentation