The important of the information presented here can *NOT* be overstated. This video should be mandatory for all Go programmers. Well done. Subbed.

i learn so much just by him casually talking

Really good stuff for those starting a library/project in Go. Thanks for filming this.

You know i neva planned to find this channel i just googled rust nd saw the rust too slow video btw its not click bait some valid points where laid there imo but am so soo happy i stayed you seem like a proper senior guy who knows his stuff .. Thanks for your guidiance Btw can you recomend books to learn golang i know others will appreciate this sir .

Thanks for shilling go. I didn't want to learn it because I didn't see anything that made it unique, but after language hopping a few times, now I see that it probably is what I needed

very well explained, thanks 🤟🏻

love the pacing, good stuff!

well done uncle rob, the last part of the video is very funny

You are absolutely right about the learning curve of Rust and the productivity in it. I love rust a lot but it just pains me to see the community pushing things like web development in Rust. it's just overkill for web apps. Rust should be used for Game Development, Database engines, Compilers, Demanding Server/Network apps, Embedded Development. just like C/C++.

He work from 29:09 t0 30:39, because as all developers in the world he forgot to save the file. In my case I have suffered enough and I configured my VSCode to auto save. Great content I'll check more videos

finally someone teaches it ! thank you!

I want to be like you when I grow old.

Great. Where can i find your all go programming playlist?

I have a background of Nodejs Express Rest APIs and React frontends. I am very interested in Golang, what books do you recommend? Great video btw

thank you very much

I’m currently considering dropping rust because it is just so stupidly hard to work in. Using your video to check out Golang! :)

Well thanks for your opinion about Rust. I was debating it with myself.

For those commenting about upper/lower case for export/private -- Using an upper or lower case letter for a public or private symbol means when you're reading through the code, you can tell INSTANTLY whether a var is public or private simply by the case of the name - you don't have to go searching for an import or export statement. Use it for a while - you will really appreciate it.

Totally agreed with the implicit last line is return value is horrible. But why do you like symbols starting capital letter is exported syntax then?

Can you make a video on why Apache license is better than MIT and BSD? That woukd be really useful! Also GPL 2 vs 3

Witch open source project can I contribute with? I'm really eager to master Go.

I faced the issue of Ctrl + L returning ^L instead of clearing the screen. It was because of the vim keybinds for my zsh, Ctrl + L only works on Normal mode.

Go newb here. Can anyone explain when to set $GOPATH? I know it's in the default C:\Users\Username\go location, but what if all my coding projects live in Z:\ ?

how do i find more of your go teachings?

nit: at 22:29 you don't show us the name of the test file!

... but.. one of the most stupid things with Go is that exporting on capital letter in symbol names. :( maybe I can get used to it. :)

这么大岁数还在写代码，厉害啊，XD

ZZzzzzzzzzzzzz......

Last line expression return value is probably the goofiest thing I've seen in modern languages. I don't know rust, but coming from Java, I found myself in a sad spot where I had to write groovy for a while, and groovy has this convention. Killing me... "return thusNSuch" is baked into all popular languages since c. Who are these edgelords with their Easter egg returns? Good thing groovy let's you write normal java. Not sorry, I'm using "return".

very opinionated