D
D
DarkMatter2016-03-11 10:35:00
go
DarkMatter, 2016-03-11 10:35:00

Which go book to choose?

Yes, I know that the official manual is better and that’s all, but I want to chew it, put it in my mouth and at first in Russian))
In general, in addition to books for 9k rubles, there are 2 books in ozone:
Go Programming Language (Alan A. A. Donovan, Brian W. Kernighan)
www.ozon.ru/context/detail/id/34671680 Go
Programming (Mark Summerfield)
www.ozon.ru/context/detail/id/19954705
Who read which one, what do you think, which one is better?

Answer the question

In order to leave comments, you need to log in

4 answer(s)
V
Vitaly Filinkov, 2016-03-11
@darkmatter

Personally, in terms of style of presentation, Summerfield is closer to me.

J
JekaMas, 2016-03-12
@JekaMas

I would suggest a light introductory book www.golangbootcamp.com
Then a deeper one www.amazon.com/Programming-Language-Addison-Wesley...
Separately, I advise on DB and Golang: https://www.vividcortex.com/resources/the -ultimate...
And on concurrency (but this book stands with caution) - www.amazon.com/Mastering-Concurrency-Go-Nathan-Koz...
And two must-read
devs.cloudimmunity.com/gotchas-and- common-mistakes... - surprisingly 90% of developers make these mistakes. Almost a desktop guide.
golang.org/doc/effective_go.html - standard, what to add here.
About interfaces here - https://habrahabr.ru/post/276981/
About how competition works in Go (and in fact runtime) - https://habrahabr.ru/company/ua-hosting/blog/269271/
What's good - most of these resources are completely free.

U
un1t, 2016-03-12
@un1t

Not a book, but a good guide - https://gobyexample.com/

@
@programrails, 2019-06-29
_

Personally, I absolutely disliked the book:
The Go Programming Language (Alan A. A. Donovan, Brian W. Kernighan)
I read it in the original in English and I can say: this is just the height of mediocrity - this book. She is strikingly clumsy on the inside. The explanation of the material causes constant irritation with its illogicality, inconsistency - some torn pieces of logical thinking. I just want to swear at the authors. But if desired, it would be possible to state and explain all the material in a simple, good and convenient way. But no - the authors clearly do not have such a desire - although, rather, they just have cockroaches in their heads. Even the English language of the authors is bad - its clumsiness - in comparison with other English-language textbooks. So much so that sometimes I had to peep into the Russian translation of this book (made, by the way, very high quality) - which I never do (I read everything only in the original, even if there is a translation - because the translation always distorts the meaning).
While reading this book, I constantly felt like a mouse that pricked, but still ate a cactus.
It's wildly infuriating their way of explaining the simple in the most complex way, as well as explaining things with the help of unfamiliar material (which will be explained at best later in the book - or not explained at all).
Or such a thing - first comes a textual explanation of the essence of the work of a piece of code - and only THEN comes this piece of code itself. While at first it is necessary to bring the code - and only then its textual explanation. This is annoying - and such an absurdity - in big and small. Some important little things are not explained at all (remain behind the scenes) - the authors forget that this may be unknown / incomprehensible to a person. The presentation of the material is not consistent enough. Too many cumbersome and overly complicated examples. In short, sheer idiocy. The authors are organically unable to present the educational material in the correct form. And this despite the fact that (seemingly) one of them was in the language development team. But, apparently, this does not mean that he is able to adequately explain the Go language. Entire chunks of chapters with complex examples have, gritting their teeth, skip (when reading). Some of the examples are senselessly over-engineered - and for some reason duplicate the material already explained.
As Zadornov said - "well, they are stupid, stupid" - it is difficult to find a more accurate description of the authors of this book.
Both options are available free of charge in electronic form in PDF, Russian, however, only as a scan (which is inconvenient, even though this scan is of very decent quality). I am still amused by the exorbitantly extortionate price for the Russian translation of the book, do not try to throw money away on this junk.
As a result - the book is read - but I feel that I didn’t have any systematic knowledge of Go, and still don’t. So, some pathetic snippets. Now I need to read something else. Kill the authors.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question