Go (GoLang)

Learning Go, 2nd Edition by Jon Bodner

When you use a blank return, the reader of your code needs to scan back through the program to find the last value assigned to the return parameters to see what is actually being returned.

I disagree with this statement. The reader of your code will still need to scan back through the program to find the last value assigned to the return parameters whether they are typed out next to the return statement or not.

GopherCon 2022: Compatibility: How Go Programs Keep Working - Russ Cox

GopherCon 2016: Porting Go to the IBM z Architecture - Bill O'Farrell

GopherCon 2016: Inside the Map Implementation - Keith Randall

GopherCon 2017: Kavya Joshi - Understanding Channels

Channels provide a simple mechanism for goroutines to communicate, and a powerful construct to build sophisticated concurrency patterns. We will delve into the inner workings of channels and channel operations, including how they're supported by the runtime scheduler and memory management systems.

Google I/O 2012 - Go Concurrency Patterns

Concurrency is not Parallelism by Rob Pike

The Why of Go

Ken Thompson: When the three of us (Ken Thompson, Rob Pike, and Robert Griesemer) got started, it was pure research. The three of us got together and decided that we hated C++. (Laughter) ... (Returning to Go,) we started off with the idea that all three of us had to be talked into every feature in the laugage, so there waws no extraneous garbage put into the lauguage for any reason.