learn the Go concurrency pattern that blew my mind 

Thank you! I’m glad that they are helpful 😊

Thank you! I’m happy it was helpful

Thanks for watching! I’m glad it was helpful 😊

Hey! Thank you so much for your support. I’ll still be posting plenty of free content as well so stay tuned😊 P.s. it really means a lot to me that you’ve stuck around for so long. Thank you for telling me. It made my day 🙂

Of course, you're an inspiration, and please, keep it going!@@kantancoding

My pleasure!

Yes, you are absolutely correct my friend. Good insight 😉 Basically, this video is to teach the orDone pattern. The context package needs its own entirely separate video (which I am currently making). I did not want to convolute the explanation of the orDone pattern with context package stuff. But! for those that want to jump ahead, this is what the code looks like replacing the done channel with the context package(the pattern does not change): package main import ( "context" "fmt" "sync" ) var wg sync.WaitGroup func main() { ctx, cancel := context.WithCancel(context.Background()) defer cancel() cows := make(chan interface{}, 100) go func() { for { select { case

It’s very useful!

Hmm, there's a discussion about this in the pinned comment where I responded to a similar comment if you're interested. But aside from that, thanks for watching and contributing 😊

what you said is actually the go way

Thanks for watching :) In my experience, there isn’t really a “best” pattern. It really depends on what you’re building so there can be a better choice of a pattern for a specific project but there is no ‘best’ pattern across the board.

Life got a bit busy but I’m back! Stay tuned for more videos 😊

@@kantancoding do more videos on teh topics like performance analysis and a typical tech stack what used mostly in the production or based on your experience, that will really give some insights which really helps budding Go lang devs.

Perf analysis sounds fun. Let me see what I can come up with

I kind of feel like "range until done" implies that we will in fact range. But if the channel is closed we won't range at all. that's why I think "range or done" is used. We'll range if the channel isn't closed or we'll be done. But of course, naming is subjective and is probably the most difficult part of programming 😆

The name "orDone" is more aligned with concepts from functional programming, like "maybe".

I don’t think I had them for this video unfortunately

Hi, I explain this in the video 🙂

Thank you! Cheers!

🤔 sorry, I cannot. That wouldn’t be fair to the people that have paid for the course.

Bro, I’m not AI. You can’t give me orders 😂🤣 Anyways, what types of videos do you want to see?

​@@kantancodingPls don't listen to him... we're enjoying it 😎