Go Systems Programming: Master Linux and Unix system level programming with Go

I had high expectations of this book but it turned out to be a very poorly written material. Supposed to be a systems programming book it very vaguely covers important systems topics. Language used is very confusing especially in chapter two. For instance information about garbage collection is extremely hard to understand. It also seems to be artificially prolonged by splitting every small sample into part 1 - including packages, part 2 - main function and multi-line command output included doesn't help either. I cannot recommend this book to anyone. There are better books to get started in Go and plenty of information online about specific systems programming tasks.

One star is "I hate it", and I don't hate this book, but also this book is not so good. It doesn't do anything well with respect to systems programming or with Go programming. The systems programming examples are trite and simple like the wc command written in Go. There were typos in the book. The book did not cover nor did the book's examples talk about the importance of stdout vs stderr and having good error codes and error messages and error handling which is 99% of systems programming. The book also cost over $50. I would recommend another book on the fundamentals of Go programming and then any generic book on systems programming.

First, I'm surprised at the number of people complaining that this book isn't conducive to learning Go. What did you expect? It's positioned as a tour of Systems Programming in Go, not Learning Go! I gave it three stars because it's not nearly as low level as the description makes it out to be. The author completely ignores the syscall and x/sys packages, which are at the heart of what systems programming is! Instead we get lame basic socket tutorials. There's nothing here that can't be found in other basic go books.

This book has some misinformation (blank identifier explanation is incorrect and never mentioned as the blank identifier), is poorly structured (returned errors in functions is glossed over on chapter 1 by assigning an error to _ and not mentioned again until chapter 3) and a number of grammatical errors that make it hard to get through.