March 7, 2026
Clockfights in the comments
The surprising whimsy of the Time Zone Database
BC locks the clocks, nerds brawl over 'US/Pacific'
TLDR: BC’s move to permanent daylight time hit the global time zone database, complete with its quirky historical notes. Commenters split between loving the whimsy and fuming over names like “US/Pacific” being treated as second-class, while standards wonks point to mailing-list debates that quietly decide what your phone shows.
Time zones are chaos, but the internet’s losing it over how charming that chaos looks inside the Time Zone Database—the giant open list your phone uses to know what time it is. British Columbia’s move to permanent daylight time just landed as a GitHub commit, and readers swooned over the quirky history notes: Britain’s WWII “double summer time,” Nashville’s “dueling” public clock, and New York’s legendary “day of two noons.” It’s history class, but with clocks throwing punches.
Then the comments exploded. One camp loves the whimsy; another wants less cute, more correct. The top hot take: why is the official-sounding “US/Pacific” treated as a “backward” alias (old name) while “America/Los_Angeles” gets top billing? Cue a naming war: team common-sense labels vs team standards-only. Memes rolled in fast—“Choose your fighter: Noon vs Noon,” and multiple replies quoting that deliciously grumpy line about the “bony, blue-fingered hand of Puritanism.” Meanwhile, the standards nerds marched in linking the ongoing tzdb mailing list drama over Vancouver’s change and how it syncs with Unicode’s CLDR (the data other software uses).
Through all the snark, one fragile peace emerged: don’t write your own time code. Enjoy the whimsy, respect the history, and maybe don’t start a bar fight over what we call “Pacific time.”
Key Points
- •The IANA Time Zone Database is widely used by software and its updates are now visible as GitHub commits.
- •British Columbia’s decision to adopt permanent daylight time is reflected in tzdb’s news file.
- •tzdb’s comments document detailed historical timekeeping changes, such as Britain’s WWII double summer time.
- •The database includes whimsical historical and cultural anecdotes (e.g., Robertson Davies’ 1947 quote, Nashville clock, NYC’s 1883 transition, Resolute Bay chronology).
- •The article underscores the recommendation to reuse established time zone data rather than implement custom time handling.