I still like physical books for the fact that I learned to study by doing a lot of highlighting and note taking. It's just a bit more of a pain in the ass to do all of that when you've just got a PDF.

You get what you pay for in a good book by a good author from a reputed publisher most of the time.

They're SO HEAVY, though, and since I live on the road my books are my heaviest possessions. I always end up giving them away when I'm done with them full of highlighted stuff which people actually seem to appreciate.

This is the last one I powered through which I recommend anyone writing go get a copy of:

https://www.oreilly.com/library/view/concurrency-in-go/97814...

The chapter on channels in Concurrency in Go https://www.oreilly.com/library/view/concurrency-in-go/97814... is a must read for anyone looking to write concurrent code in Go. There are many "rules" you need to follow with channels to avoid shooting yourself in the foot that I haven't seen summarized in blog posts/official go docs

I'll preface this with: I am in no way affiliated with O'Reilly. I would suggest this book for a deeper look into Go's concurrency http://shop.oreilly.com/product/0636920046189.do While Go does have channels to allow concurrent communication, it also allows the use of mutexes for concurrency similar to c/c++. And on the flip side, there's things like libmill in C that will give you Go-like concurrency. It is also worthwhile looking at how Go's memory model works (it's similar to tcmalloc). Additionally, looking at the implementation of channels maybe interesting for you. It consists of a buffer that gets memcopy'd with mutexes for synchronization, granted, that's a very simplified view of it.

I would suggest you to read the book "Concurrency in Go", by Katherine Cox-Budai, 2017: http://shop.oreilly.com/product/0636920046189.do