• Go 1.6 compiler slowed down
• Recent commit cuts compile times by 40%
• Compile times may return to pre-Go 1.4 levels in Go 1.7 release
• CloudFlare blog post on building simple static analysis tool for Go
• Discussion of using static analysis tools and existing options like New Relic
• Iron.io's experience with Ruby, its performance issues, and migration to Go
• Planning for future performance loads and identifying areas that require optimization
• Discussion about the performance of a Go project and how it outperforms customer needs
• Mention of RocksDB as a persistence layer in CockroachDB and IronMQ
• Raft consensus protocol implementation
• Introduction to go-oauth2-server, an OAuth2 server written in Go
• Rqlite, a distributed SQLite database written in Go with Raft support
• Discussion about the ease of building distributed systems using technologies like etcd and RocksDB
• Discussion of GPUdb and its status as possibly "vaporware"
• Introduction to Syncthing, a peer-to-peer syncing tool written in Go
• Features and benefits of using Syncthing for syncing files across machines
• Mention of alternative methods for file syncing compared to Dropbox
• Discussion of Caddy, a web server/reverse proxy with built-in Let's Encrypt support
• Caddy's embeddability and potential for programmatic configuration
• Introduction to Viper, a command-line tool for pulling in environment variables and config files
• Use cases and features of Viper
• Discussion of the Cobra library and its benefits for writing command line tools in Go
• Mention of Steve's Hugo project as a precursor to Cobra and other libraries such as Viper and Pflag
• Introduction of Gin Web Framework/ API framework, which simplifies web development in Go
• Plug for goa, a code generation tool that creates API implementations from Go DSLs
• Discussion of the benefits of using goa, including readability and the generation of Swagger JSON files for documentation
• Clarification on how goa works, including defining APIs in Go code with anonymous functions
• Discussion about Go database access layers, specifically GORM
• Introduction of GORMA plugin for Goa framework
• History of using Go at Iron.io, including adoption before 1.0 release
• Comparison with other languages like Java and Ruby
• Role of early adopters in promoting the language's growth
• Importance of community passion and interaction in driving interest in the language
• Productivity with C++ vs Go
• Go's concise syntax and small number of keywords
• Lack of code generation needs in Go development
• Early pain points with Go (library availability)
• Comparison to other languages like Java and Ruby
• Performance optimization in the Go community
• Allocations and memory management in Go programming
• Discussion on static analysis tools for Go programming language
• Importance of memory allocation management at high scale (1M requests/sec)
• Challenges of tracing down allocations in large codebases
• Hiring challenges for Go developers and experience with training new hires
• Adoption of containers, specifically Docker, by the company
• Use of Docker to enable easy testing and deployment of customer code
• Discussion of Docker and containerization
• Experience with early bugs in Docker and how they were handled
• Advantages of using containers in development and production environments
• Future prediction for Docker and containerization taking over the computing world
• Shoutouts to open-source projects, including GopherJS, polymer bindings, and gocyclo
• Docker and containerization
• fsnotify library for monitoring file system changes
• Upcoming major announcement by Travis' company
• GoTime.fm podcast and newsletter subscription information
• GitHub suggestions for show topics or guests
• Appreciation for Travis Reeder's contributions to the Go community