my notes from @jprbnsn and @brnstz's GopherCon recap

recap.md

GopherCon Recap

by @jprobinson and @brnstz

Talk Highlights

• Rob Pike's Hello Gophers! includes a history of "hello world"
• Russ Cox: From C to Go how they made go
• Best Practices For Production Environments pdf, will download
• 2014-talks github repo
• Videos

Best Practices

• Full list from Peter Bourgon's presentation

My highlights below, hopefully accurate.

Formatting

• go fmt on save.
• vim users should get vim-go

Use the stdlib packages

• flag
• log
• testing
  • note: you can assert equality using reflect.DeepEqual - I hadn't thought of that.
• how to run integration tests separately: // +build integration || go test -tags=integration more info
• go get -d will download package source code but not go install it

Compiling

• how you handle external dependencies depends on... how important your project is
• vendor dir name: depends, are you building a library or a binary? more info
• use go build in dev, make in production (there was some discussion on this that I missed)

Code Coverage

• gocover-cobertura for integration with CI servers like jenkins; github page has amusing disclaimer...

History of Go

Rob Pike: Hello Gophers! includes a history of "hello world"

They started with C. Other languages influenced Go too.

Russ Cox: From C to Go

• programming in go is fun...
• "One big gofix"
• "You are not expected to understand this."

Using C in Go

Basically, you import "C". More info at C? Go? Cgo! on the golang blog.