Go 1.27 Lands with Generics Maturity and UUID Support
Go 1.27 shipped with generic methods (not just generic types), a built-in UUID package that replaces the ubiquitous github.com/google/uuid dependency, and automated migration tools via 'go fix'. Developers in the thread are actively running the migrators on existing repos and calling out the UUID addition as long overdue. The generics discussion is notable: people who left Go before generics landed are now reconsidering it for new projects.
The pattern: Go is in a maturity phase rather than an innovation phase, and the community is fine with that. Each release is filling in gaps that felt embarrassing before, like needing a third-party package for something as basic as UUIDs. The discriminated unions / algebraic data types debate is still alive but there's no indication the core team is moving there.
The counterpoint from the thread is that some feel Go is still too conservative. Discriminated unions would meaningfully reduce bugs in a lot of Go code, and the reluctance to add them remains a sticking point for developers coming from Rust or Kotlin.
So what?
If your team avoided Go because the pre-generics ergonomics were rough, 1.27 is a reasonable moment to revisit. The built-in UUID package alone removes one minor but annoying dependency management decision. For teams already on Go, run 'go fix' now before your codebase accumulates more technical debt against the new idioms.