June 22, 2026
When 7000 becomes the main character
UUID: NewV7() always generates a UUID with 7000 on browsers (Golang)
Go’s fancy ID maker kept spitting out “7000” in browsers, and the comments got spicy
TLDR: Go’s new ID generator appears to repeat the “7000” section in browser-based apps because browser clocks are less precise than expected. Commenters fought over whether that makes it a real bug or just an awkward design edge case, with plenty of eye-rolling at the “works as designed” defense.
A tiny bug report turned into a full-on comment-section courtroom drama after developers noticed Go’s new ID generator kept producing browser-made codes with the same suspicious-looking “7000” chunk every time. To non-coders, that basically means a tool meant to add some unpredictability was acting weirdly predictable in web browsers. And yes, the community immediately zoomed in on that repeating number like it was a glitch in the Matrix.
The strongest reactions split into two camps: the “this is a real bug, fix it” crowd and the “technically it’s working as designed” crowd. That second stance got mocked fast. One commenter summed up the mood with a sharp “Missing the forest for the trees,” which is internet-speak for: congratulations on being technically correct while ignoring the actual problem. Another commenter explained the likely cause in plain terms: browsers often only tell time in rough millisecond chunks, so the code was accidentally filling part of the ID with the same value over and over. They even pointed to Temporal, a newer browser time feature, as a possible fix.
Then came the veteran energy: one commenter basically sighed that this kind of thing is always messy, because time precision, counters, and multiple programs generating IDs at once can all turn simple-looking solutions into chaos. The humor here is that the bug looks tiny — just “7000” — but the comments made it sound like a soap opera about clocks, browsers, and developers arguing over whether a flaw is a flaw if the spec can explain it away.
Key Points
- •A GitHub issue reports that Go's `uuid.NewV7()` generates UUIDs containing a fixed `7000` segment in browser environments.
- •The issue is identified as `#80084` and describes the problem as affecting `NewV7()` output under browsers.
- •The reported environment is `go1.27rc1 darwin/arm64`.
- •The reproduction command uses `GOOS=js GOARCH=wasm go1.27rc1 run main.go` with `go_js_wasm_exec`.
- •The reporter expected the `000` portion of the UUID segment to contain random bytes instead of remaining fixed.