I'm coming from the JS world (feeling the same fatigue you mentioned in another video) and also dabbling with Go on my spare time. Hoping to see more great Go content from you as you learn and explore the language!
Really like your GO related videos, what kind of resource you are using to learn Go and kubernetes, is it youtube, udemey course or just documentation?
Love your videos man they've been very helpful the last 18 months as I relearn web dev. Nervous about the job landscape for junior devs but either way, channels like yours make it seem more fun than anything else.
Once we enter the channel into the Reader function, why are we still dealing with the WaitGroup variable wg and wait for its Done? can we sync up the main function other than waiting for wg?
I've a general question. Would you say that Go is a great place to place my time on compared to Rust or is it the opposite way around? * I don't have a specific goal yet by learning a new language.
I’ve never used rust, but if you want to actually be productive and build something real, I’d pick go. If you just want to learn new stuff, rust seems fine
One of your previous videos you mentioned that public methods in Go start with an uppercased character. Why is the make method with lowercase, isn't that a public method of some sort? It is not defined in your code, and still you can access it. Something totally different, or something missing the convention?
@@WebDevCody he didnt say they suck but they arguing about why they work way they do. like they are nil if u dont put anything into them etc... u are really fast learner and doing great in Go!
He was just saying there were some weird behaviors with channels like closed channels return 0 values and panic when you write to closed channels. He said it would have made more sense for channels to return an error
You would use a buffered channel to implement semaphores in go. That way you can spin up as many goroutines or threads as you've allocated the buffered channel
There's alot of concurrent primitives to avoid race conditions like atomic.Value or atomic.Pointer and sync.Map and as you mentioned using mutex on shared resources. It's really not hard to avoid. Go also has a race flag that helps you detect potential race conditions
Not only go i fast, but also really fast and great. Using express + typescript eating my machine. 8 gb of ram is barely capable of doing the development
I'm coming from the JS world (feeling the same fatigue you mentioned in another video) and also dabbling with Go on my spare time. Hoping to see more great Go content from you as you learn and explore the language!
Wow The fact Go allows you to bypass a million third party libraries is great. These videos are really helpful
This is the reason why I spent the past year only coding in Golang....it's just such a nice experience.
Really like your GO related videos, what kind of resource you are using to learn Go and kubernetes, is it youtube, udemey course or just documentation?
chatGPT and experimenting by just building stuff
Straight to the point. Really good video, with zero bushing around the bushes.
Love your videos man they've been very helpful the last 18 months as I relearn web dev. Nervous about the job landscape for junior devs but either way, channels like yours make it seem more fun than anything else.
Doin great babe ❤
Once we enter the channel into the Reader function, why are we still dealing with the WaitGroup variable wg and wait for its Done? can we sync up the main function other than waiting for wg?
Go is Go-ing over my head xD i tried rust too but the learning curve is steep.
Go mention !!!
I have not learned Go but are WaitGroup and Channel like Thread pool and (un)bounded buffer in traditional terminologies?
Sounds accurate i think? Ask ChatGPT
Would be awesome if you could do a video on error handling in Go, I hear it has a really good primitives for it.
If I had to interpret it with what I already know, can I say that this is similar to an event loop?
I've a general question. Would you say that Go is a great place to place my time on compared to Rust or is it the opposite way around?
* I don't have a specific goal yet by learning a new language.
I’ve never used rust, but if you want to actually be productive and build something real, I’d pick go. If you just want to learn new stuff, rust seems fine
One of your previous videos you mentioned that public methods in Go start with an uppercased character. Why is the make method with lowercase, isn't that a public method of some sort? It is not defined in your code, and still you can access it. Something totally different, or something missing the convention?
That’s a built in global. No clue why they decided to make it lowercase
I thought you were referring to Go TH-cam channels lol
Is it really a round robin?
What’s so special (beyond the cleaner syntax) about Go channels versus queues in Python and Java?
I think queues are more of a data structure in python and java, but channels is a communication method built into go (that kind of acts like a queue)
would be very interesting your opinion about fiber framework which gives typescript developers easily get start
what do u think about golang backend frameworks which one do u want to learn or want to use
idk I'm just using the built in net/http
go is so great, u really dont need a framework
Theo: GO channels suck!
Cody: GO channels are awesome!
oh, did he recently say channel suck?
@@WebDevCody he didnt say they suck but they arguing about why they work way they do.
like they are nil if u dont put anything into them etc...
u are really fast learner and doing great in Go!
He was just saying there were some weird behaviors with channels like closed channels return 0 values and panic when you write to closed channels. He said it would have made more sense for channels to return an error
What theme is that
Bearded theme stained blue
Thank you
The wait group is almost exactly like semaphores
You would use a buffered channel to implement semaphores in go. That way you can spin up as many goroutines or threads as you've allocated the buffered channel
You should touch on races as well. Go routines are amazing but they have sharp edges that hurt 😂
as in two go routines accessing the same variable which requires a mutex? is that what you mean by races?
There's alot of concurrent primitives to avoid race conditions like atomic.Value or atomic.Pointer and sync.Map and as you mentioned using mutex on shared resources. It's really not hard to avoid. Go also has a race flag that helps you detect potential race conditions
Goroutines do NOT run on different threads. This is concurrency, not parallelism
Not only go i fast, but also really fast and great. Using express + typescript eating my machine. 8 gb of ram is barely capable of doing the development