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 UUID

Table 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)

Hosts

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

• (00:00) - Prologue