Discovering Go

My experiences of learning Go, and why I think it's a great tool to learn.

Transcript

1. Go @zefer
2. Go
3. Write robust, high-performing Go programs… without being an expert.
4. Opinionated
5. Minimal
6. C-like syntax package main import "fmt" func main() { greeting := "hello" fmt.Println(greeting) }
7. Practical, not beautiful
8. Statically compiled $ go build
9. Portable $ scp myapp myserver:/var/www
10. FAST compilation
11. Cross-compilation $ GOOS=linux GOARM=6 GOARCH=arm \ go build
12. Statically typed animal := "gorilla" animal = false cannot use false (type bool) as type string in assignment
13. Garbage collected
14. Unused variables package main func main() { greeting := "hello" } Won’t compile! greeting declared and not used
15. type SimpleLogger struct{} func (l SimpleLogger) log(msg string) { fmt.Println(msg) } Not OO
17. Standard library
18. package main import ( "fmt" "net/http" ) func handler(w http.ResponseWriter, r *http.Request) { fmt.Fprintf(w, "Hello world!") } func main() { http.HandleFunc("/", handler) http.ListenAndServe(":8080", nil) } Web
19. Error handling import "net/http" func handler(w http.ResponseWriter, r *htttRequest) { err := doSomethingThatMightFail() if err != nil { w.WriteHeader(http.StatusInternalServerError) } }
20. Error handling if err != nil { // Handle your error. }
21. Performance
22. Whitespace $ gofmt
23. Workspaces & imports package main import "github.com/zefer/mothership/websocket" func main() { }
24. Imports package main import "github.com/golang/glog" func main() { }
25. Concurrency
26. Goroutines func hey(msg string) { fmt.Println(msg) } func main() { go hey("joe") hey("zefer") }
27. Channels func main() { messages := make(chan string) go func() { messages <- "ping" }() msg := <-messages fmt.Println(msg) }
28. Networking, concurrency & command line tools
29. Experiences
32. My naive code was really robust
33. I didn’t need as much help as I expected
34. Much less maintenance
35. Write robust, high-performing Go programs… without being an expert.
36. Verbose
37. Awesome performance
38. Compiler errors are nice
39. gofmt
40. My newbie code looked okay
41. “When writing the Go function, I started at the top and typed until I got to the bottom. And that was it. There aren’t very many ways to write this function in Go. I expect that most Go programmers, given the same set of helper functions, would have written it almost identically. Because of gofmt, I don’t even make formatting decisions.” - Rob Napier
42. Now
43. Write robust, high-performing Go programs… without being an expert.
44. Thanks. @zefer