Published: March 14, 2026
Runtime: 1:06:40
Episode: Episode 62

The Least Contentious Proposal in the History of Go

Edition Regular 1:06:40

Subscribe & Listen

For members

More from this conversation

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.

Explore podcast memberships

Chapters

00:00 Prologue 1:05
01:05 Chapter 1: Catching Up with the Panel 2:02
03:07 Chapter 2: The UUID Proposal 5:26
08:33 Chapter 3: GitHub as a Discussion Platform 3:35
12:08 Chapter 4: The History of UUID Versions 4:12
16:20 Chapter 5: The Flawed Ecosystem Survey 11:36
27:56 Chapter 6: The Proposed API: New, NewV4, NewV7 3:37
31:33 Chapter 7: Library Design Philosophy vs. the Go Team's Approach 10:18
41:51 Chapter 8: The Default Debate and the RFC's Intent 9:00
50:51 Chapter 9: Code of Conduct Double Standards 8:46
59:37 Chapter 14: Cultural Communication and the Path Forward 4:46
01:04:23 Epilogue 2:17

Show notes

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.

Notes

proposal: uuid: add API to generate and parse UUID