After 8 Years, Go Finally Adds a Native UUID Package

At 3 a.m. the author noticed the ubiquitous import github.com/google/uuid in his go.mod and wondered why it hadn't been promoted to the standard library after being used in over 800 projects.

Go 1.27 will natively support the uuid package

package uuid

id  := uuid.New()               // returns a v4 UUID, 122 bits of randomness
v7  := uuid.NewV7()              // time‑ordered UUID, ideal for database indexes
parsed, _ := uuid.Parse("f81d4fae-7dec-11d0-a765-00a0c91e6bf6")

Key design details include:

Type compatibility : the UUID type is defined as [16]byte, allowing seamless conversion with existing code.

Parsing flexibility : Parse accepts four formats – with hyphens, without hyphens, with the urn:uuid: prefix, and with surrounding braces – matching how developers previously wrote parsers.

Nil and Max as functions : they are functions rather than variables to avoid the pitfalls of mutable exported values (the author notes a past incident with google/uuid.Nil).

Default version : the package generates v4 UUIDs by default because their pure randomness avoids hotspot issues in sharded databases, even though v7 offers better insert performance.

Why the addition now? The standard library’s conservative philosophy

The author reflects that the standard library aims to be the ecosystem’s “greatest common denominator” rather than a cutting‑edge experiment. The proposal succeeded not because UUID technology is new, but because the third‑party google/uuid library proved over eight years that the community truly needs a stable, built‑in solution.

Interestingly, the new package deliberately omits version detection (e.g., uuid.Version()) following RFC 9562’s recommendation to treat UUIDs as opaque identifiers, embodying Go’s “less is more, convention over configuration” ethos.

Final thoughts

The author likens technical evolution to cooking porridge: too high a flame burns, too low cooks slowly. Each standard‑library addition balances practicality with restraint, and the new uuid package exemplifies that careful trade‑off.