Mate, you're the next Ben Awad at the rate your going. Your vids picked up on my algorithm today and I'm really impressed with the quality and content you are putting out.
Thank you very much for this comprehensible quick start on concurrency patterns. I'd love to see a deep dive on concurreny in combination with HTTP servers, context deadlines etc.!
I am enjoying the content, keep it up, my sense is that you are probably your own worst enemy when it comes to improving, so keep it up. Say less, but clearer.
Topic you covered is good. But the speed in which you are explaining is difficult for Non-native listeners. You may need to slow down a little. I felt that you are super duper fast.
It does not know that. Basically a Mutex only ensures that the code between the Lock and Unlock call has to finish before another goroutine can enter this codeblock. If another goroutine wants to enter this codeblock it has to ´wait´ until the lock is lifted
Hey can somebody explain why in the mutex loop if i becomes 0 and then 1 the map isn't unblocked? Is it because the goroutine gets started and the loop continues and starts the next one? But shouldn't the first routine be the first one to lock and the value always ends up with 0?
From what I understood is that since it's concurrent, they are all running at the same time. So 0 isn't necesarally the first one in this case. So the mutex would take one at random out of all of them, unblock it. But since everything was running at the same time. It could get one value. Hence, a random result everytime
when creating a tutorial / educational video - you need to be precise. examples: go routines are running in threads, not processes. go func you used are not methods - they are functions.
Mate, you're the next Ben Awad at the rate your going. Your vids picked up on my algorithm today and I'm really impressed with the quality and content you are putting out.
I appreciate it! Time will tell but I am super happy with how things have been going
he's gonna have to be more sus if he wants to be the next ben awad lmao
Yes please, broken down more, more examples, real life use case and then a sub playlist on youtube!
finally someone made me understand the difference between concurrency and parallelism
It always amazes me how easy it is to work with concurrency/parallelism in Go, feels like a better version of async/await.
Completely agree
Thank you very much for this comprehensible quick start on concurrency patterns. I'd love to see a deep dive on concurreny in combination with HTTP servers, context deadlines etc.!
Your explanation of advanced concepts made learning easy . Thank you for simplifying the complex!
Loved you way you explained these, this is a great overview!
You were the only one That mande me understand Channels, thank you so much
That is one of the best explanations of this I have ever seen!
Mutex looks like Lockers in java, but simplier to use, thank you for your work, getting many insights!!!
Mind-blowing explanation
Thanks for this really amazing representation of Goroutines man!
Yes... Ben talking about Go!!! 🙂
Lovely vid, thank you for the crisp explanation Ben!
Super good. Thanks for the explanation.
Such a clear explanation 😁Many thanks
Great video, clear explained, thanks Ben! 👍
you're gonna have 200k in probably 3 years from now, great content
This is really helpful to understand, thanks for this!
Awesome man! Take love for making concept base go tuts
I am enjoying the content, keep it up, my sense is that you are probably your own worst enemy when it comes to improving, so keep it up. Say less, but clearer.
This is great and simple. Thanks for the video
Good day sir, hopefully we can see a more advanced of use cases on Go routine. Earn a sub!
such an informative video .. clearly understood!
Thanks John!
Thanks for this, I believe muted has clicked for me now
great explanation bro thank you very much
really helpful .......keep it up bro !!!!
brilliant.
Best
Was looking for Go Concurrency vid from you. Finally! Any plan for advance use case of Go Concurrency and Parallelism?
Yep ;)
hey man
what color theme do u use in this video?
Would the mutex example still throw an error if yoe were to use a diffrent key in each goroutine?
Topic you covered is good. But the speed in which you are explaining is difficult for Non-native listeners. You may need to slow down a little. I felt that you are super duper fast.
yes Ben, a little slower pls because it's hard to follow
So when using channels we don't need waitGroup?
One thing I don't understand that how does mu.lock() knows what memory it is blocking?
It does not know that. Basically a Mutex only ensures that the code between the Lock and Unlock call has to finish before another goroutine can enter this codeblock. If another goroutine wants to enter this codeblock it has to ´wait´ until the lock is lifted
Does this work the same for file IO? Asking for a friend.
Hey can somebody explain why in the mutex loop if i becomes 0 and then 1 the map isn't unblocked? Is it because the goroutine gets started and the loop continues and starts the next one? But shouldn't the first routine be the first one to lock and the value always ends up with 0?
From what I understood is that since it's concurrent, they are all running at the same time. So 0 isn't necesarally the first one in this case. So the mutex would take one at random out of all of them, unblock it. But since everything was running at the same time. It could get one value. Hence, a random result everytime
Bro i tried to use go and like it but usecase is limited ? What we can't build with go i mean? And why there are limited jobs on LinkedIn
High performance web servers, background workers, and CLI apps
Also go is very popular among DevOps and Cloud stuff.
when creating a tutorial / educational video - you need to be precise.
examples: go routines are running in threads, not processes. go func you used are not methods - they are functions.
God I thought I turn on 2X, but it turn out I didnot.
Why do you use wg.add(1) two times B4 each goroutine instead of wg.add(2) once?
For the purposes of the example to make it clear why I was incrementing each time. One wg.add(2) does the same thing
🥢🥢🥢