3 ms·
From the webpage Note added January, 2022: This document was written for Go's release in 2009, and has not been updated significantly since. Although it is a
by MattSteelblade 4y ago
From the webpage
Note added January, 2022: This document was written for Go's release in 2009, and has not been updated significantly since. Although it is a good guide to understand how to use the language itself, thanks to the stability of the language, it says little about the libraries and nothing about significant changes to the Go ecosystem since it was written, such as the build system, testing, modules, and polymorphism. There are no plans to update it, as so much has happened and a large and growing set of documents, blogs, and books do a fine job of describing modern Go usage. Effective Go continues to be useful, but the reader should understand it is far from a complete guide.
- ash 4y agoIt's best to consider Effective Go as the book, like the timeless K&R ("The C Programming Language" book).
- _ph_ 4y agoThe very same "K" has co-authored the equivalent Go book: https://www.gopl.io/ https://www.gopl.io/ I can only recommend it, though I wished they would make a second edition including all the new language features. But for the base language, it is still great.
- Beltalowda 4y agoI suspect the biggest annoyance for people new to Go using the gopl book will be the changes to the ecosystem (modules, go get changes, etc.) You can learn a language without learning about $new_feature_x perfectly fine; this is something you can just pick up later. But if you run in to trouble with the first chapter because the commands no longer work then that kind of sucks.
- pjmlp 4y agoMore as a reviewer though, minute 47. https://cppcast.com/unix-history/ https://cppcast.com/unix-history/
- mseepgood 4y agoThere's an actual Brian Kernighan book on Go: "The Go Programming Language". (gopl.io)