Great video Ben. I’ve really been enjoying your channel lately. I’ve just started learning Go and backend development a few weeks ago. I’ve been doing front end for a long time. I find your videos like this one really helpful in understanding some of the concepts and features of Go.
I have been doing frontend for a long time and it's beginning to grow on me. I switched to go recently and i chanced on channel. great one and a new fan
Congrats on the initiative to building these tutorials, it makes it much easier for people to get into GO, and your style of teaching is very practical. Keep going and the channel will grow for sure
I've just recently came across your channel and I must say there so much quality content. Specially being so transparent with your InsiderViz examples. Thank you for sharing with us.🙌🏽
You are covering great topics with these 10-15 min vids! They are also super informative for people who have knowledge in other languages to get a grip on Go ! Cheers
I love those concepts/conventions type of content when learning new stuff. Please include more for more advanced topics as well. Quickest I grasped something in a while was with this video. Thanks.
Just a suggestion, you should really explain the concept of multiple returns before explaining the concept of := reassignments. The := reassignments concept is making use of the multiple returns concept so for those who are new to Golang might be confused on the a, err := foo() syntax
I love the scoping feature (capital letters) in Go compared to JavaScript. No need to worry about writing "export" for each function or learn different standards such as CJS or ESM.
what is the use case for "func(s Showcase)" - referencing the struct by value? because the compiler is clearly not complaining about this. you can still call the SetName method of the struct. SetName can read the values of the struct but cant modify them?
it doesn't work that way in Go unfortunately. Multiple returns are independent values and both must be accessed because not accessing a variable is invalid in Go, unlike in Python where multiple returns = a tuple
Thanks, man for your replies but after a bit of googling, I found out Its enabled by adding "window.commandCenter": true," in user setings.json or the UI.
Ok, I'll just say the new keyword and builtin is useless. I've never seen it used in out production code. we just use var to have things initialized to zero values, including nils for pointer types. For a language that likes to have a single way of doing things, "new" is doubly useless.
