Why understanding concurrency in Go is so important 

Pass by pointer if its object, pass by value if its primitive.

@@twitchizle pass by pointer if its concurrent, be it primitive or object

yep, immutable data is thread safe

Exactly my thoughts, thanks for writing this. An important additional benefit of using channels is that they can buffer messages. A mutex blocks all coroutines waiting on it, whereas a buffered channel can be written to even when the select at its other end is not ready to process the message. So instead of waiting on the mutex, a coroutine pushes a message into the buffered channel and carries on with its work. This is called handling backpressure.

it's a footgun, a powerful tool of the language you could easily screw yourself over with if not careful

@@WebDevCody im not one for splitting hairs over definition pedantics, and i dont disagree with the havoc this could cause. However, i just dont think this is the “biggest” (as the original video title stated) weakness of Go. Sure, you might face this problem starting out if you’re new to concurrency or channels at a lower level, but once you learn them, these issues dont really come up frequently in practice. As you write more Go, whenever you see a go routine you just kinda build up a mental note to check for referencing something outside of the channel scope or check for needing a mutex. However, nil pointers and seg faults in Go come up quite often, especially when communicating with an external API or poorly crafted Go bindings. There’s a reason folks call null a “billion dollar mistake.” Having non-required struct properties is a far bigger footgun in Go in my perspective, having used Go as my primary backend language for coming up on 4 years. Nil pointers are just in your face constantly in Go, while incorrectly passing data between channels and the main thread or using a mutex isnt as frequent of a problem.

@@hamm8934 I went ahead and updated the title anyway 🤣 too many people didn’t like the word foot gun and I never said the word once in the video anyway. I haven’t used go long enough to know the true footguns, so I’ll just avoid the word

@@WebDevCody fair :) great video none the less Hope you keep liking go and dont give up just yet on htmx and templ! Cheers

@@hamm8934 I’m trying to hang on but I’m missing nextjs already 😆

Basic concurrency handling, shared mutable state requires a mutex if multiple threads want to access it at once, I guess javascript/python just hides all of this away

This is more so learning pains when going a little lower level

Got em

@lemurza5236 I think you can consider it a foot gun since go compiler doesn't flag variables accessed within go routines that aren't locked.

this is just a skill issue not a footgun by any means its designed perfectly

You’re the best!

Must be nice to be a babe to someone :,) Ya’ll are goals

Yap, there's atomic package built in.

Elaborate more please

Yes, because in Rust it's a footcrab instead.

On the contrary. Rust apps are full of data race. Go apps are cleaner.

yeah you have to choose between footgun or arc

Rust cultist is everywhere

what would you call it?

Nah just SQL directly

btw you are the best

Love you!