First chapter of Kernighan and Donovan's new Go book [pdf]

"But it has comparatively few features and is unlikely to add more. For instance, it has no implicit numeric conversions, no constructors or destructors, no operator overloading, no default parameter values, no inheritance, no generics, no exceptions, no macros, no function annotations, and no thread-local storage."

Re: First chapter of Kernighan and Donovan's new Go book [pdf]

#5

Post by middleclick » Mon, Oct 19, 2015, 4:55 PM UTC

Question for the Go experts out there: does it make sense to buy this book to learn Go or are there better tutorials/books?

Re: First chapter of Kernighan and Donovan's new Go book [pdf]

#6

Post by vezzy-fnord » Mon, Oct 19, 2015, 4:57 PM UTC

Interesting to see that the direct lineage from Pike's prior languages and CSP experiments is reaffirmed. I wrote about this here earlier, with some notable disagreements in response: https://news.ycombinator.com/item?id=9711639

Re: First chapter of Kernighan and Donovan's new Go book [pdf]

#7

Post by [deleted] » Mon, Oct 19, 2015, 4:57 PM UTC

[deleted]

Re: First chapter of Kernighan and Donovan's new Go book [pdf]

#8

Post by claystu » Mon, Oct 19, 2015, 4:57 PM UTC

I have no idea what they will specifically say regarding calling C from Go, but the table of contents says that part is only going to be about five pages.

I really wish they would beef up this portion of the book.

Re: First chapter of Kernighan and Donovan's new Go book [pdf]

#9

Post by Omnipresent » Mon, Oct 19, 2015, 4:58 PM UTC

To those in the Go community:

- What is Go well suited for other than network programming? - Why might one decide to write the backend API of their web app in Go, compared to say Grails, Python etc.

Re: First chapter of Kernighan and Donovan's new Go book [pdf]

#10

Post by claystu » Mon, Oct 19, 2015, 4:59 PM UTC

vezzy-fnord wrote: post #6

Interesting to see that the direct lineage from Pike's prior languages and CSP experiments is reaffirmed. I wrote about this here earlier, with some notable disagreements in response: https://news.ycombinator.com/item?id=9711639

Nice to see Oberon getting its fair share of credit too