I've watched two of your Go videos now and I'm amazed at how quickly you can convey the lessons. I wish I'd had this pace and style of teaching for all the other languages I've learnt in my 35 year career. Please keep them coming. 💚
For those whose having a hard time understanding the concepts covered, i highly recommend the book 'Concurrency in Go' by Cox Buday, however if you're just starting to learn the language, 'Go in action' by Kennedy and Martin, is more suited then, follow it up with buday's book.
Currently taking a distributed systems course in college that recommends implementation in go so I did quite a bit of searching to crash course go. After watching this and the 12 minute video, i feel like I can just jump in and immediately excel in that course. Concurrency is just done SO well in go.
This is the best best best best best best Go's Concurrency explanation! Recommended for all beginner learning Go's Concurrency. Very clear, simple, and details! The best! Thank You Jake
Extremely easy to follow and understand. Great video. The way you deconstructed this by showing really simple examples and each step adding more logic and/or syntactic sugar is the way I learn myself so this video suited me perfectly.
This is by far the best channel I’ve found for programming. Perfectly paced for those of us with experience in other languages who need to pick up a new one quickly for a project. Thanks friend
It's impressive that I watched your html in 12 minutes video a decade ago and it's the video that made me fall in love with coding at the time. Now that I'm learning go I'm also watching your video. I guess the student never outgrows the teacher.
After completing the golang tour, I was still not completely sure about the details of channels, goroutines, and select. I had read slightly about wait groups separately but this really brings it all together neatly and succintly. Great video and one I will probably be coming back to.
@@VishalAnand24 I'm interested in the performance differences between Go and your C# library. Could you please share your results? Also how many lines of code were needed for you to write it in C#?
@@Peshyy making those channels is very easy, since you already have ConcurrentQueue which wrapper nicely would do exactly that. But to be honest I didn't have the same reaction - I just use observables to do similar things, and they can be "converted" to tasks to nicely wait for them to finish. This isn't as magick as you think :P
@@SimonWoodburyForget I dont agree with you. Go is meant to be compiled to machine code and GC is just another lib linked into the executable. Meanwhile C# compiles to IL and machine code is produced on runtime, GC resides in the dotnet runtime. Sure JITing is fast, but it still has some overhead. On the other hand I do like C# syntax more, but thats just personal taste...
This and your other Go video are phenomenal for those who want to tie everything together. Instead of just programming in Go, I can think and understand in Go! Very helpful - thanks.
Thanks Jake! Great explanation delivered at the perfect balance for new-comers wanting to understand Go's concurrency model. This is so much better than some of the other YT videos I've seen where the code is literally typed out as if that is enough for the viewer to understand how it is working and all hangs together!
Man, I tried to learn Go in their original tour, and got confused many times in the concurrency section, but you, @ Jake Wright clear them all. Thank you sooo much
From what I understand, the `go` keyword puts a function into a task/promise, so that it can be fulfilled asynchronously or in the background. I had also (incorrectly) thought that all the calls, asynchronous or synchronous, had to finish before the program ended!
Wow pretty cool stuff. I just took an OS class and learned about how complicated concurrency is, and we went over the whole producer/consumer pattern where you need to manage your own conditional variables and mutexes. It seems like channels handle literally all of this for you at runtime!
Wow. Always heard about how go is good at concurrency. This demo really gives that impression to a has-never-used-go guy like me. And the syntax is neat.
The anonymous goroutine wrapper function at 5:10 is exactly the structure my brain was telling me to make, where I already had multiple "complex" synchronous functions that I wanted to simply leave up to the implementor to decide when to make it run in another goroutine.
Man this is awesome 🔥🔥 By watching this video, I got to understand each and every single details about concurrency in go. This is one of the best video on Golang... Thanks buddy 😊... Cheers ✌️
@3:40 goroutines dont define their own suspensions or reentry point (joint). Go follows a model of concurrency called the "fork-join" model. These gorutines fork anytime during the execution of program to be run concurrently with its parent. The word JOINT refers to the fact that at some point in future these concurrent forks will join back together, its called the joint point. Since you dont have a joint point both functions are queued to be executed and then they just never got the chance to run before main goroutine exits. ==> To fix this we use sync.WaitGroup which added the joint point :)
Holy Shit!!! Go is really amazing. It really makes it easier for you to consume tough concepts like Mutex, Semaphores, and Concurrency which takes a lot of time, knowledge, and understanding when implementing in other languages. Really excited to try it out.
@3:26 Just for fun here is the Python version of the program: import time from threading import Thread def main(): Thread(target=count, args=("fish",)).start() Thread(target=count, args=("sheep",)).start() def count(thing): while(True): print(thing) time.sleep(0.5) main()
QUESTION: hi jake, first of all thank you for the video, very good content. In the last script with workers, i'm not quite sure why the results loop wait for the result channel to send info. I mean, the main function is executed, and once its get to the last loop, it should go through it regardless the workers finished or not. would be understandable if you have a range over the result channel, for outputting the fib numbers hope this make sense, i have been thinking a lot. can anybody clarify? thanks!!
I haven't even worked in Go either, but this looks extremely similar to Python 3.5+ coroutines. Although coroutines add a nice layer of abstraction on top of async/await, you still have to think about thread-safety if you want to achieve true parallelism with them. At least, that's how it goes in Python. And I can't see, how any other impure language can be any different.
Pretty cool! I have no experience in Go, but the approach is somewhat similar in Rust and both are far clunkier then Erlang when it comes to concurrency constructs. Massive progress though in modern languages. I really like the relative simplicity(for a imperative language) of the tools available in Go. Both Rust and Erlang would be more efficient at actual paralellisation of the execution due to the extra constrains they take to remove side effects, but for most things (and competent planning) Go would be really close.
Great stuff!!! Coming from the PHP world! this is awesome! Thanks for this videos explaning everything very well! I watched this one and go in 12 minutes :)
Thanks.. It was a wonderful introduction. I have a huge database containing multiple tables wherein I would like to execute multiple queries in concurrence. I have 3 questions: 1) Can I execute multiple SQL Statements in concurrence ? 2) I will be executing the SQL Queries on a popular RDBMS. Now is it necessary for the RDBMS to support concurrence. If yes, please answer for Oracle 11G and Mysql.
In other words I want to know whether concurrency (which is linked to processor cores)can be made use of even if the RDBMS does not support concurrency ? 3) Assume that I am executing 2 SQL statements in concurrence. Assume further that both these SQL Statements populate a common table with their output, how will I ensure that when the results of an SQL Statement is being populated, the 2nd SQL Statement will wait ? In simple words I do not want a 'deadlock' kind of thing. Whether this is possible using go ?
Fantastic lesson. Question: At one point you mentioned that Go had not yet solved the Halting Problem. Do you think this will be included in the next release? 😉
The throughput of knowledge transfer in this video is insane! You are able to cover so much in just 15 minutes. That's amazing.
yeah it's crazy, you even get a taste of what the halting problem is, completely unsolicited
04:18 WaitGroup
06:13 Channel
08:36 Deadlock and Channel closing
10:08 Non blocking buffered Channel
11:25 Select statement
13:23 Worker pool pattern
Dude, you are the man!
isnt the last one just multi threading?
this is the best overview of goroutines and channels that i have ever seen. well done.
I've watched two of your Go videos now and I'm amazed at how quickly you can convey the lessons. I wish I'd had this pace and style of teaching for all the other languages I've learnt in my 35 year career. Please keep them coming. 💚
Extremely easy way to convey the concepts. No wonder why TH-cam shows up at the top, despite its small size.
For those whose having a hard time understanding the concepts covered, i highly recommend the book 'Concurrency in Go' by Cox Buday, however if you're just starting to learn the language, 'Go in action' by Kennedy and Martin, is more suited then, follow it up with buday's book.
Currently taking a distributed systems course in college that recommends implementation in go so I did quite a bit of searching to crash course go.
After watching this and the 12 minute video, i feel like I can just jump in and immediately excel in that course. Concurrency is just done SO well in go.
This is the best best best best best best Go's Concurrency explanation!
Recommended for all beginner learning Go's Concurrency.
Very clear, simple, and details! The best!
Thank You Jake
Extremely easy to follow and understand. Great video. The way you deconstructed this by showing really simple examples and each step adding more logic and/or syntactic sugar is the way I learn myself so this video suited me perfectly.
No one explained this simple for go lang in any TH-cam channels. Thanks for the great work.
The illustration at 8:13 is the clearest explanation that I've ever seen
This is by far the best channel I’ve found for programming. Perfectly paced for those of us with experience in other languages who need to pick up a new one quickly for a project. Thanks friend
1:35 "And then I'm gonna sleep for half a second"
Me at night
hahahahahaha
2:05 "So it will just do that until I kill it"
Dwight Schrute with his chickens
Bro I was going to comment "Every college student ever" on the same thing.
This video is too great. not only shows how to work with goroutines, but also write a clean and optimized code using golang too. thanks a lot man
It's impressive that I watched your html in 12 minutes video a decade ago and it's the video that made me fall in love with coding at the time. Now that I'm learning go I'm also watching your video. I guess the student never outgrows the teacher.
Perfect explanation of concurrency in Go. The best I've found on TH-cam 👍
This is an amazing lesson. please do more Go videos.
This is short, and crisp but damn at point. Good job mate !!
Great video. Finally someone explained it properly in depth, but still very straightforward, simple and understandable. Thank you.
Some of the absolute best Go content on youtube. Thank you!
At first, I didn't understand it at all, but after a one repetetion, it become crystal clear! Thank you, Jake.
After completing the golang tour, I was still not completely sure about the details of channels, goroutines, and select. I had read slightly about wait groups separately but this really brings it all together neatly and succintly. Great video and one I will probably be coming back to.
this is by far the best tutorial about concurrency in go. thanks man, keep up the good work!
Not gaing to lie, this video really makes me want to write a few cpp libraries to emulate this behaviour. It's gorgeous!
I did the same in C# when I first saw it
@@VishalAnand24 I'm interested in the performance differences between Go and your C# library. Could you please share your results? Also how many lines of code were needed for you to write it in C#?
@@Peshyy making those channels is very easy, since you already have ConcurrentQueue which wrapper nicely would do exactly that. But to be honest I didn't have the same reaction - I just use observables to do similar things, and they can be "converted" to tasks to nicely wait for them to finish. This isn't as magick as you think :P
or just use go lol
@@SimonWoodburyForget I dont agree with you. Go is meant to be compiled to machine code and GC is just another lib linked into the executable. Meanwhile C# compiles to IL and machine code is produced on runtime, GC resides in the dotnet runtime. Sure JITing is fast, but it still has some overhead. On the other hand I do like C# syntax more, but thats just personal taste...
By far the best practical explanation of go routines, love it
By far the best tutorial about Go Concurrency, THANK YOU
Great overview of concurrency in go. The pace of the video was spot on and touched the key points.
This and your other Go video are phenomenal for those who want to tie everything together. Instead of just programming in Go, I can think and understand in Go! Very helpful - thanks.
The best explanation about goroutines and channels. Good job dude. 👍
Thanks Jake! Great explanation delivered at the perfect balance for new-comers wanting to understand Go's concurrency model.
This is so much better than some of the other YT videos I've seen where the code is literally typed out as if that is enough for the viewer to understand how it is working and all hangs together!
Absolute champion. Literally one of the best videos about programming I've ever seen. Thank you very, very much
Man, I tried to learn Go in their original tour, and got confused many times in the concurrency section, but you, @
Jake Wright clear them all.
Thank you sooo much
This is brilliant.. Haven't ever seen such a packed yet clear video tutorial. Great work buddy
I didn't fully understand go concurrency until I found this video, thank u soo much.
That's a pretty good introduction to go's concurrency, just that, no more, no less, straight to the point, exactly what I was looking for.
From what I understand, the `go` keyword puts a function into a task/promise, so that it can be fulfilled asynchronously or in the background.
I had also (incorrectly) thought that all the calls, asynchronous or synchronous, had to finish before the program ended!
Man answered all the questions I had from watching the other tutorials
Why would anyone thumbs down this video!!!! good job Jake, you are so right
For Java developers learning Go :
05:38 = CountDownLatch
07:42 = ReentrantClock + Condition
14:52 = SingleThreadExecutor
16:07 = FixedThreadPool(4)
5:38 or thread join, 7:42 ReentrantLock you mean. Good comparison. Much less code to write in Go it seems.
i should say, your really good at teaching. i can grasp it easily
lucidly explained a seemingly complex topic. Thank you
You are a god send. I would have failed out of university years ago if it wasn't for people like you.
your videos is amazing! Really clean and precise, it's everything that a programmer want from tutorials
What a great short and to the point introduction to Go concurrency. Great examples. Thanks!
best go concurrency video so far on youtube
Wow pretty cool stuff. I just took an OS class and learned about how complicated concurrency is, and we went over the whole producer/consumer pattern where you need to manage your own conditional variables and mutexes. It seems like channels handle literally all of this for you at runtime!
I must say this is a short but very concise intro to concurrency in go. I liked it.
This is the best explanation I've found till now, thanks!
Learning English I have to say that your pronunciation is very clear and soft.
I wish classes could be like this. Just give me the simplest, fastest explanation, and let me pause/rewind as I need.
A few days ago, I started playing Exopunks, a Zachtronics programing game and I really think it illustrates some of these concepts very clearly.
Though most of the example are from gobyexample.com i still think every go beginner should watch this. Jake's explanation is superb.
This is the best demonstration Iǘe seen in go channel. Thanks!
Finally a video which explains it all in simple understandable words! Thank you!!😃
This was the best explanation and illustration I've seen yet. Thank you!
Wow. Always heard about how go is good at concurrency. This demo really gives that impression to a has-never-used-go guy like me. And the syntax is neat.
The anonymous goroutine wrapper function at 5:10 is exactly the structure my brain was telling me to make, where I already had multiple "complex" synchronous functions that I wanted to simply leave up to the implementor to decide when to make it run in another goroutine.
Man this is awesome 🔥🔥 By watching this video, I got to understand each and every single details about concurrency in go. This is one of the best video on Golang... Thanks buddy 😊... Cheers ✌️
This is honestly such an amazing tutorial. Great job!
@3:40 goroutines dont define their own suspensions or reentry point (joint).
Go follows a model of concurrency called the "fork-join" model.
These gorutines fork anytime during the execution of program to be run concurrently with its parent.
The word JOINT refers to the fact that at some point in future these concurrent forks will join back together, its called the joint point.
Since you dont have a joint point both functions are queued to be executed and then they just never got the chance to run before main goroutine exits.
==>
To fix this we use sync.WaitGroup which added the joint point :)
Newbies: this is pretty confusing and irrelevant to the point Jake's making
@@zerosandones701
Thanks. Well described. I was pleasantly suprised that Go has such a nice and compact syntax for concurrency stuff.
Best video ever to understand go concurrency.
Thanks !!
Wow, I got impressed how you explained very easily you got the point really well. Thank you!
Thanks! This was just what I needed to wrap my head around the subject 👌
Probably the best explanation I've seen yet, nice one 👍
Holy Shit!!! Go is really amazing. It really makes it easier for you to consume tough concepts like Mutex, Semaphores, and Concurrency which takes a lot of time, knowledge, and understanding when implementing in other languages. Really excited to try it out.
Thanks for this video. just started learning Go for work
A very good explanation indeed! Will definitely watch all of your other videos
I really like the pictorial representation of concepts.
Loved this video, I finally understand this
Thank you so much for this video, we are trying to optimize our worker concurrency and this is exactly what I need
Some people are good teachers! Amazing Job!
Easy explanation with brilliantly organized examples!!
Thanks Jake. Great introduction, all the relevant concepts of concurrency explained in simple terms with illustrative examples. Thank you very much!
I am impressed by how simple go makes concurrency. It is way simpler in Go than in Python.
@3:26 Just for fun here is the Python version of the program:
import time
from threading import Thread
def main():
Thread(target=count, args=("fish",)).start()
Thread(target=count, args=("sheep",)).start()
def count(thing):
while(True):
print(thing)
time.sleep(0.5)
main()
This is GOLD.. Thanks a lot Jake
So well explained. After 4 years still on the money.
Wow those channels are awesome. Way better than waiting for promises to resolve in js
The best vid about concurrency in go
He knows his stuff. Thanks, Jake 👏
QUESTION:
hi jake, first of all thank you for the video, very good content.
In the last script with workers, i'm not quite sure why the results loop wait for the result channel to send info.
I mean, the main function is executed, and once its get to the last loop, it should go through it regardless the workers finished or not.
would be understandable if you have a range over the result channel, for outputting the fib numbers
hope this make sense, i have been thinking a lot. can anybody clarify?
thanks!!
Having never looked at Go, this seems infinitely better than all this async-await nonsense I've had to deal with in other languages...
I haven't even worked in Go either, but this looks extremely similar to Python 3.5+ coroutines. Although coroutines add a nice layer of abstraction on top of async/await, you still have to think about thread-safety if you want to achieve true parallelism with them. At least, that's how it goes in Python. And I can't see, how any other impure language can be any different.
async await are amazing, what the fuck are you talking about?
basically you when you dont know about a programming language you will start bragging about it !
Thank you for such a short and clear video
Best tutorial on concurrency ever.
Very clear. Really understandable, very consistent explanation. Brilliant, amazing, great, cool, nice and super.
Thank you.
How is the job and result channel being controlled for access of multiple worker for them? Encapsulated within Chan? Interesting quick intro!
Very good video, clear explanations, great examples! Thank you!
Best explanation for Beginner
Can you create a full course on go (like. Creating a Micro Service in Go from Scratch)? your explanations are very good.
Pretty cool! I have no experience in Go, but the approach is somewhat similar in Rust and both are far clunkier then Erlang when it comes to concurrency constructs. Massive progress though in modern languages. I really like the relative simplicity(for a imperative language) of the tools available in Go. Both Rust and Erlang would be more efficient at actual paralellisation of the execution due to the extra constrains they take to remove side effects, but for most things (and competent planning) Go would be really close.
Please more videos on Go, this is brilliant!
This explanation is so clear and to the point, thank you!
Great stuff!!! Coming from the PHP world! this is awesome! Thanks for this videos explaning everything very well! I watched this one and go in 12 minutes :)
Thanks.. It was a wonderful introduction.
I have a huge database containing multiple tables wherein I would like to execute multiple queries in concurrence.
I have 3 questions:
1) Can I execute multiple SQL Statements in concurrence ?
2) I will be executing the SQL Queries on a popular RDBMS. Now is it necessary for
the RDBMS to support concurrence. If yes, please answer for Oracle 11G and Mysql.
In other words I want to know whether concurrency (which is linked to processor cores)can be made use of even if the RDBMS does not support concurrency ?
3) Assume that I am executing 2 SQL statements in concurrence.
Assume further that both these SQL Statements populate a common table with their output, how will I ensure that when the results of an SQL Statement is being populated, the 2nd SQL Statement will wait ? In simple words I do not want a 'deadlock' kind of thing. Whether this is possible using go ?
you have great understanding of the language and thanks for the tuts.
This was a great, to the point explanation of concurrency in Go. Very helpful!
Thanks for that prez, was perfect to illustrate the/some strength of GO and get me fired up about it.
Off to install it and start coding.
Extremely curious about your job search.
@Intelligence Injection Concurrency is not basic...
Fantastic lesson. Question: At one point you mentioned that Go had not yet solved the Halting Problem. Do you think this will be included in the next release? 😉
I imagine it will take an indeterminate amount of time
Very sharp and precise explanation