@TheHellishFrog
This is the gold of the tutorial - I subscribed immidately.
@Miles-co5xm
Please keep making videos, algorithm is working
@ZohaibZafar-eh5ov
Amazing tutorial Mr Green Tea, i love your teaching style of hands on approach. your videos helped me alot traveling through the rust learning curve. just one minor nit-pick at 6:16 it says thread "process that can execute code", i wouldn't call thread a process, it is better to call them "mini-processes" that are inside a process. other wise for the rest of the video your explanations were excellent. say blessed Mr Green Tea.
@Hellbending
This tutorial is handsdown the best thing that I have viewed/consumed in terms of explaining how async works and is super helpful in understanding some of the things that Tokio brings in a really really really concise manner - I so greatly appreciate the time and effort you put into your videos man ❤ plz don’t be one of the great YouTubers that ghosts us 🥲🥲😅❤❤❤❤
@zubiarfan
Your explanations are very good and clear. Thank you
@cristianalinbelu8297
Subscribed, excelent videos man. Thanks and keep up the great work you are doing. I really like your teaching skills.
@priyanshukumawat4142
Loved this content man <3. Greetings from India
@bresent
Hidden gem
@adrian_sp6def
15:11 You said that things execute in parallel, but You also said at the beginning that async functions does not execute across threads so no parallelism there. I am confused
@zanfur
You very much do not need to copy the stack when changing threads. What actually happens is that you just use a different stack by changing the stack registers to that from the other thread. Think of it like moving a string: you copy the pointer to it but not the data itself.
@rafaelcostavilla2722
Thank you so much for explaining the difference between tasks and threads, and how to tokio deal with them! Apart from that, I realised the part about the channel implementing a not used receive_messages function. Could you please explain to me why?
@test143000
Async in computer science usually means an operation that doesn't block a calling thread and completes asynchronously to it so the thread can continue to do some useful work and later check for operation completion status. For example, a file operation can be completed asynchronously by a kernel thread, later the thread that started this operation checks or waits for operation completion. I think the earliest implementation at operating system level was asynchronous (overlapped) IO in Windows NT. Async can also be implemented at a device driver level. For example, when a network card driver or disk driver completes an IO request when processing an interrupt that is sent by a device on IO completion. This was implemented in Windows NT.
@test143000
Actually, switching threads for the same process is cheap compared to most operations, like file IO. The stack doesn't need to be copied. Switching to another virtual address space is expensive, which happens when a thread for another process is scheduled.
@Cerealkiller8642
Awesome
@pyroblighter8401
Good explanation
@stanrock8015
Where is part 1-4? Can’t find them
@ZohaibZafar-eh5ov
7:55 so it was asynchronous execution thread that did 9/11
@dog4ik
I dont like green tea
@learning_rust