Great job! Your course has been helping me a lot in learning Golang. It's one of the best resources I've found on TH-cam for delving deeper into understanding advanced concepts. I'm really grateful to have found this channel, and thank you for taking the time to create and make this course available.
How do you make sure that two goroutines are not looking at the same file? I know they'll both have the same path when they do, so you can remove the duplicates, but they would waste time looking at the same file
If the two goroutines are reading from the same channel then go takes the responsibility of synchronizing between the goroutines. In other words, two goroutines are not going to get the same value from a channel..
I believe time runs automatically via the built-in shell utility, which might make it a little bit imprecise, try to do something like bash -c '/usr/bin/time yourbinary' instead
This is literally the art of Software Engineering!
Great job! Your course has been helping me a lot in learning Golang. It's one of the best resources I've found on TH-cam for delving deeper into understanding advanced concepts. I'm really grateful to have found this channel, and thank you for taking the time to create and make this course available.
Infinite gratitude is the feeling here! This course is pedagogical masterpiece. Thank you Matt!
It took me a few days to grasp all concepts but this is really an amazing concurrency example
straight to point and this must watch for go devs at all levels
This was a really good one! Thank you for putting this up Matt!
absolute masterpiece
another masterpiece'
Wow.. Just WOW !!! This content
How do you make sure that two goroutines are not looking at the same file? I know they'll both have the same path when they do, so you can remove the duplicates, but they would waste time looking at the same file
If the two goroutines are reading from the same channel then go takes the responsibility of synchronizing between the goroutines. In other words, two goroutines are not going to get the same value from a channel..
channels are concurrent safe
how did you measure time effectively? If I use "time" command I get almost around same values for all three versions...
I believe time runs automatically via the built-in shell utility, which might make it a little bit imprecise, try to do something like bash -c '/usr/bin/time yourbinary' instead
Maybe your num of directories and files are not large enough. Try your Downloads or Documents folder.