วีดีโอ

Thank you, this has been really helpful ❤

Just adding this comment for the people who have started this series. First: This is the best series on Go, and it's free. Second: It is almost 21 hours in total. If you watch and do the hands-on with Matt, it should take you more than a week (probably two weeks) to complete.

This is literally the art of Software Engineering!

Http sockets do not exist

Best hello world example I have ever seen awesome! I had no idea how you could make that so educational but you did.

This playlist is priceless

good explanation teacher Matt

Very different from the programming languages I am used to. Loving this course. Thank you, Matt!!

Learning Go from scratch, just read about Channels and goroutines. This video is really helpful to understand the details relevant for practical use. Nice job!

This is a piece of gold. Thank you for your amazing work

Really appreciate these quality content on go. Thank you Matt !

Idk why, but I find syntax confusing. I have 10+ years of experience in writing in JS, PHP, C++ and python. I though python is fucked up with its' syntax of inventing the wheel by trying to optimize everything. But then I found Go

This with benchmarking is like having x-ray vision

Returning to this video to let people know that the homework series are also neat, even as a viewer. If you don't want to write the "homework", treat it like a lecture because that's how he discusses the homework anyway. Each homework in the series builds on the topics discussed prior to it. Homework #4 and #5 especially are a nice little demonstration of taking naive read/write operations in a REST API (#4), and improving it to avoid race conditions using simple usage of mutexes (#5). He verifies the states of #4 and #5 code using the `-race` option. Please like this so people see immediately.

Definitely the best course of Go, Thank you Matt!

Finally I understood why it is named Closure. Best go class! Thanks Matt.

just want to say a thank you after completing your series. i am really grateful that you posted such content for everyone to see and benifit from. you presented it in a nice and kind way. Thank you Matt.

At 39:28, can't we just use & to get the address and then call ScaleBy on that?

For anyone using Go >=1.22, the behavior where the variable i captures the same location and prints the same value (e.g., 4) when a closure is called has been fixed in the latest versions. PS: Great explanation Matt, really grateful for these classes and your explanations

Great video, thanks

This should be paid!

Was doing advent of code this year, decided to use go to learn it deeper and faced this very strange behaviour So basically never append to or modify values in slices that were derived from array/another slice…😅 Thank you for explanation!

Looking forward to new courses matt. thank you for your course...

Thank you! This is great course!

Great content! Thank you!

Great video!

starting my transition to cloud engineering with this series. Thanks

Amazing

when i run this code every things works fine not need to shadow i variable why ? package main import "fmt" func main() { s := make([]func(), 4) for i := 0; i < 4; i++ { s[i] = func() { fmt.Printf("%d -- %p ", i, &i) } } for i := 0; i < 4; i++ { s[i]() } } result is 0 -- 0xc000104040 1 -- 0xc000104048 2 -- 0xc000104050 3 -- 0xc000104058

Matt, your wealth of knowledge clearly shows when teaching. Amazing.

this content is free. this is worth paying for. even better than so called paid courses. I wish you make more courses on linux and systems programming in general, or is there somewhere I can purchase your courses.

This is an amazing course. Thanks so much!

"it's not to scale" lmao great stuff. Thanks for sharing

What are the obvious reasons for not writing software in Go? @ th-cam.com/users/clipUgkxd6EcsGOtqi-MQJNNp9YpQdJgO8-IXWWP?si=EQtE3c4vS2pvsdpd

th-cam.com/video/MDB2x1Di5uM/w-d-xo.html Thats me most of the time im trying to code anything.

Invaluable source of knowledge about Golang and just programming in general. Thank you for such a great work you do.

Seeing your face besides the code is distracting

Man you teach so good!

either me finish this or this finish me

just finding these videos now cant wait to go through them

what i understand from this, someone should validate. If you are ever going to have any reason to slice an array.. you are better of creating a slice from the beginning and let go handle the underlying array.

I still dont understand the closed over here

thank you for the detailed lessons.

f*ck me, this is the best course I've watched so far on Go... and it's free. Thank you, sir.

this legend is inspiring a new generation of capable, competent and cracked Go developers!

Hi Matt. great videos. Thank you for posting and sharing them !! Note: @18:53 of slice examples z := a[0:1] you mention that z become a slice that points to first two elements of a. is it correct to say that as z will have only the first element from array a?

Sorry, but I think C or even c++ is way easier to understand and use

Array is immutable by nature , But can be mutated using a slice🥲. This concept kills me.

Hello Matt, I want to start with thanking you so much for the amazing content you are providing it have been very helpful for me. and second I was just wondering if GOMAXPROCS is kind of misleading with hyperthreading, as far as I know hyperthreading would be beneficial only in case multiple threads are requesting to use different execution units. however in our case when the scheduler create double the physical cores it still wouldn't get the expected parallel execution. what I mean is, for 8 physical cores processor that supports hyperthreading it would read it as 16, open 16 threads and expect 16 parallel goroutines to run in parallel however only 8 max would run which "feels" kind of misleading. would like to hear your opinion on that and thanks.

thanks, you really teach very well