Question for the Go experts out there: does it make sense to buy this book to learn Go or are there better tutorials/books?
First chapter of Kernighan and Donovan's new Go book [pdf]
11–20 of 233 posts
Re: First chapter of Kernighan and Donovan's new Go book [pdf]
#12Re: First chapter of Kernighan and Donovan's new Go book [pdf]
#13Re: First chapter of Kernighan and Donovan's new Go book [pdf]
#14To 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.
You'll get a lot of different opinions on this. I'll just speak based on my experience, since Python was my primary language before coming to Go.
Everything I used to use Python for, I can do faster in Go. The notable exception to this is statistical analysis, as Go does not have any FORTRAN bindings[0], whereas Python does (through Numpy & co.). I still use a combination of Python, R, and other languages for this.
I came to Go for the static typing and native concurrency[1], but I stayed because I'm more productive in it. Python and Go are about equally fun to write, but because I can build things much faster in Go, it ends up feeling more rewarding overall, given that my time is limited.
If you don't really have a pressing need for anything else, you can stick with Python. But I found Python to be slow to develop in and cumbersome, and after trying Go out, I realized I was 100x more productive in it.
[0] apparently this may no longer be true; if so, that's exciting news!
[1] this was also before Python had built-in async. I still prefer Go's concurrency model and syntax, but at least Python has this as an option now.
Re: First chapter of Kernighan and Donovan's new Go book [pdf]
#15To 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.
Moreover, I love static deploys and cross compilation with Go. Compile your app (even to Windows!), copy it to a server, simply run it as a single binary. No dependency management, no apt-get & easy_install & pip, it just runs.
Re: First chapter of Kernighan and Donovan's new Go book [pdf]
#16Question for the Go experts out there: does it make sense to buy this book to learn Go or are there better tutorials/books?
Also, check out the blog posts for more information on specific topics: http://blog.golang.org/. They are really well written.
Re: First chapter of Kernighan and Donovan's new Go book [pdf]
#17Question 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]
#18Question 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]
#19To 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.