Dylan's back this week joining Kris and Matt to tackle Go's UUID proposal (#62026). What Dylan thinksshould have been the least contentious proposal in the history of Go. The panel digs into the proposed API's shortcomings, the flawed ecosystem survey used to justify it, and why the Go team's library design philosophy doesn't hold up. The conversation builds into a broader critique of community dynamics and code of conduct double standards.As always, we've got supporter content! This week that includes the psychological cost of dismissive governance and who actually gets heard, the opaque proposal review process, what the Go developer survey numbers really say about community trust, and a debate over whether GitHub is even the right platform for proposal discussions. 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.No episode of Break this week. We'll have more aftershow episodes soon! In the meantime, catch up on previous episodes at https://break.show.Thanks for tuning in and happy listening!Notes:proposal: uuid: add API to generate and parse UUIDTable of Contents:Prologue (00:00:00)Chapter 1: Catching Up with the Panel (00:01:05)Chapter 2: The UUID Proposal (00:03:07)Chapter 3: GitHub as a Discussion Platform (00:08:33)Chapter 4: The History of UUID Versions (00:12:08)Chapter 5: The Flawed Ecosystem Survey (00:16:20)Chapter 6: The Proposed API: New, NewV4, NewV7 (00:27:56)Chapter 7: Library Design Philosophy vs. the Go Team's Approach (00:31:33)Chapter 8: The Default Debate and the RFC's Intent (00:41:51)Chapter 9: Code of Conduct Double Standards (00:50:51)Chapter 14: Cultural Communication and the Path Forward (00:59:37)Epilogue (01:04:23)Socials:WebsiteBlueskyThreadsX/TwitterLinkedInInstagram

Another week, another Kris & Matt duo episode! This week, they're picking up where Bryan Cantrill's "Complexity of Simplicity" framework left off and asking what it means for Go's future. Kris argues Go is squarely rebellious (simple and emergent) and that the community needs to stop appealing to the Go team and start owning the ecosystem. The episode builds to a (potentially unpopular) proposal: deprecate the error interface.As always, we've got supporter content! This week that includes Oxide's counter-cultural approach to hiring, a riff on tech industry irony and title inflation, and a deep dive into why Go couldn't ship general-purpose coroutines. 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.No episode of Break this week. We'll have more aftershow episodes soon! In the meantime, catch up on previous episodes at https://break.show.Thanks for tuning in and happy listening!Table of Contents:Prologue (00:00:00)Chapter 1: Catching Up and Guest Plans (00:00:56)Chapter 4: Go as a Rebellious Language (00:05:38)Chapter 6: Go's Unique Position: Rebellious and Revolutionary (00:09:40)Chapter 7: Modules, SemVer, and Where Go Missteps (00:12:55)Chapter 8: Stop Appealing to the Go Team (00:16:01)Chapter 9: Building a Community-Owned Ecosystem (00:24:46)Chapter 10: Recapturing Go's Excitement (00:32:09)Chapter 11: The Problem With the Error Interface (00:41:01)Chapter 12: Multiple Returns and Deprecating the Error Interface (00:48:06)Epilogue (00:56:13)Socials:WebsiteBlueskyThreadsX/TwitterLinkedInInstagram

Welcome back to Break, a Fallthrough aftershow! Kris and Matt continue the Go repository structure conversation by zooming in on the details. The pair discuss what they dislike about database libraries in Go, with a particular distaste for mocking. Then they have an extended discussion of Bryan Cantrill's "Complexity of Simplicity" quadrant framework from TalosCon. They argue Go was rebellious, but modules have been slid it into the accreted quadrant.Enjoying the aftershow? Let us know on social media! If you prefer to watch instead of just listen, head over to YouTube where you can watch this episode of Break!Thanks for tuning in and happy listening!Chapters:Prologue (00:00:00)Chapter 1: Go's database/sql Package Design and Magic Imports (00:01:24)Chapter 2: SQL Mocking Is Painful, Just Use a Real Database (00:04:23)Chapter 3: Global Side Effects and Why Nobody Will Fix Go's SQL (00:08:07)Chapter 4: Go Package Design and the Limits of Import Paths (00:12:31)Chapter 5: Bryan Cantrill's "Complexity of Simplicity" Quadrant Framework (00:17:49)Chapter 6: Where Does Go Actually Fit? Rebellious, Not Revolutionary (00:24:15)Chapter 7: Go Is Sliding Into "Accreted" Territory (00:33:04)Epilogue (00:39:30)Socials:WebsiteBlueskyThreadsX/TwitterLinkedInInstagram

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)Socials:WebsiteBlueskyThreadsX/TwitterLinkedInInstagram

Another week, another Kris & Matt duo episode! This week, they're talking about Go. They cover the recent generic methods proposal by Robert Griesemer, results from the 2025 Go Developer Survey, some highlights of the 1.26 release, and more!As always, we've got supporter content! This week that includes the survey's tooling data, a deep dive into GOPATH nostalgia and why Go Workspaces can't save the AWS SDK's 70,000+ tags, Kris's research into the entire Go module proxy, and a structural argument for why the module system's base premises don't hold. 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.No episode of Break this week. We'll have more aftershow episodes soon! In the meantime, catch up on previous episodes at https://break.show.Thanks for tuning in and happy listening!Table of Contents:Prologue (00:00:00)Chapter 1: Go Generic Methods Proposal (00:00:46)Chapter 2: Go 1.26 Release Highlights (00:17:07)Chapter 3: Go Developer Survey: Trust & Leadership (00:25:42)Chapter 4: Survey Challenges: Idioms, Features & Error Handling (00:36:22)Epilogue (01:08:23)Socials:WebsiteBlueskyThreadsX/TwitterLinkedInInstagram