Another week, another Kris & Matt duo episode! This week, we're digging into Go codebase structure, package design, and why the community keeps struggling with the same problems. The conversation starts with a Gopher Slack discussion about how to arrange Go code, moves through package hell and dependency cycles, and ends with a look at community health.

As always, we've got supporter content! This week that includes Go's missing project boundary and why internal is a blunt instrument, real world package design patterns, and how modules broke the elegant simplicity of Go's database/sql driver pattern. Not a supporter yet? Fix that today by heading over to https://fallthrough.fm/subscribe where you'll get not only extra content but also higher quality audio. Sign up today!

If you prefer to watch this episode, you can view it on YouTube.

This week's episode of Break continues the conversation. Kris and Matt dissect the magic underscore imports in database/sql, argue you should just test against a real database, and then spend the back half debating where Go lands in Bryan Cantrill's "Complexity of Simplicity" quadrant framework. Watch it on YouTube or listen with your favorite podcasting app! Learn more by going to https://break.show/ep/29.

Thanks for tuning in and happy listening!

Table of Contents:

• Prologue (00:00:00)
• Chapter 1: Catching Up: Snow, Life, and Episode 60 (00:00:57)
• Chapter 2: The Go Repository Structure Problem (00:05:50)
• Chapter 3: Package Hell and Dependency Cycles (00:10:19)
• Chapter 6: The Go 1 Compatibility Promise (00:18:06)
• Chapter 9: The Community Must Lead (00:26:11)
• Chapter 10: The Dying Gopher Slack and Community Fragmentation (00:37:45)
• Chapter 11: "You're Holding It Wrong" (00:45:11)
• Chapter 12: GopherCon vs. RustConf: The Energy Gap (00:53:24)
• Epilogue (00:59:32)

Hosts

• Website
• Bluesky
• Threads
• X/Twitter
• LinkedIn
• Instagram

• (00:00) - Prologue