Daniel sent us this one — he wants to talk about time zones and daylight saving time. He wrote a piece about something called the Time Zone King and the TZDB database, maintained by a small community in California, which apparently every Linux computer on the planet depends on. He also wants to clarify that UTC is not the same as GMT — UTC is time zone agnostic and doesn't observe daylight saving. The big questions he's throwing at us: how did time zones and daylight saving actually come into being? What are the real controversies around daylight saving? What happens if we just abolish it? And here's the one that got me — could we just standardize on one offset globally and have everyone adjust their working hours instead of their clocks?
Oh, this is a beautiful knot of history, politics, and software engineering. And that dependency chain Daniel mentioned — the TZDB — is genuinely one of the most underappreciated pieces of infrastructure on the planet. Every time your phone knows what time it is, every calendar invite that lands at the right hour across continents, every server log timestamped correctly, it's touching this database maintained by a handful of volunteers. But before we get into that, quick note — DeepSeek V four Pro is generating our script today. So if something sounds unusually coherent, that's why.
Now, the Time Zone King — who is this guy and why does he have a crown?
Scottish-born Canadian railway engineer. In eighteen seventy-six, he missed a train in Ireland because the printed schedule said p.instead of a., and he decided that the entire planet needed to get its act together. He proposed a worldwide system of twenty-four time zones, each one hour apart, all referenced from a prime meridian. Before that, every town ran on its own local solar time. When the sun was directly overhead, that was noon. Boston was about twelve minutes behind New York. There were something like one hundred forty-four different local times just in the United States.
If you were taking a train from New York to Boston, you'd arrive twelve minutes before you left?
Well, not exactly, but that's the confusion. The railroads were the forcing function. They had to publish timetables, and if every stop had its own local noon, scheduling was a nightmare. In eighteen fifty-three, a head-on collision in Rhode Island killed fourteen people because two trains were running on different local times. So the railroads imposed their own time zones before any government did. November eighteenth, eighteen eighty-three — the "Day of Two Noons" — every railroad station in North America synchronized to four time zones. Clocks in the east were set back, and noon happened twice that day in some places.
Wait, the railroads just did this unilaterally? No congressional vote?
Private industry solved the problem because the government was dragging its feet. Congress didn't officially codify standard time zones until the Standard Time Act of nineteen eighteen — thirty-five years after the railroads had already done it. And that same act also introduced daylight saving time, which is a whole other story.
Let's stay with Fleming for a moment. He proposes this in eighteen seventy-six, but the prime meridian wasn't settled yet, right? There was a fight over that.
Oh, big fight. The International Meridian Conference in Washington in eighteen eighty-four — twenty-five countries sent representatives. France wanted the prime meridian to run through Paris. Britain pushed for Greenwich, because by that point something like seventy-two percent of the world's shipping already used British nautical charts based on the Greenwich meridian. The French abstained from the final vote and kept using the Paris meridian for another twenty-seven years. They called it "Paris Mean Time, retarded by nine minutes and twenty-one seconds" instead of just saying Greenwich Mean Time. The pettiness is magnificent.
That is spectacularly French. So we get standard time zones, and then daylight saving gets bolted on later. Who do we blame for that?
The standard answer is Benjamin Franklin, but he was joking. In seventeen eighty-four, he wrote a satirical letter to the Journal of Paris suggesting that Parisians could save money on candles by waking up earlier. He proposed cannons firing at dawn and a tax on window shutters. It was pure satire. The actual origin of daylight saving as a serious proposal comes from a New Zealand entomologist named George Hudson. In eighteen ninety-five, he proposed a two-hour shift so he'd have more daylight after work for collecting insects. His proposal was mocked.
So daylight saving time exists because a guy wanted more bug-hunting hours.
That's the earliest serious proposal. But the version that actually got implemented came from William Willett, a British builder, in nineteen oh seven. He noticed people still had their curtains drawn on summer mornings and got furious about the wasted daylight. He self-published a pamphlet called "The Waste of Daylight" and lobbied Parliament until his death in nineteen fifteen. He never lived to see it implemented. Germany was the first country to adopt it, in April nineteen sixteen, as a wartime fuel-saving measure. Britain followed a month later. The United States adopted it in nineteen eighteen with that Standard Time Act I mentioned.
The first country to actually do it was Germany, during a war, to save coal. Not exactly the cheerful "more time for picnics" story you usually hear.
Right, and the history since then is chaotic. repealed daylight saving after World War One, then brought it back for World War Two — it was called "War Time" and it was year-round. After that, there was no federal law. Cities and states could choose their own start and end dates. By nineteen sixty-five, the state of Iowa alone had twenty-three different pairs of start and end dates across different municipalities. The airline industry lobbied hard for the Uniform Time Act of nineteen sixty-six because scheduling flights was becoming impossible.
Twenty-three different daylight saving schedules in one state. That's almost impressive. So where are we now? I know Arizona and Hawaii don't observe it.
Arizona opted out because of the heat. When the sun stays up until eight or nine p.in Phoenix in July, you don't want an extra hour of daylight — you want the sun to go down so things can start cooling off. Hawaii doesn't observe it because being near the equator, daylight hours don't vary much across the year anyway. The sun rises and sets within about a ninety-minute band year-round. And then you have the weird cases: Indiana didn't fully adopt daylight saving statewide until two thousand six. Before that, some counties observed it, some didn't. The Navajo Nation observes daylight saving while the Hopi Reservation, which is completely surrounded by the Navajo Nation, does not. You can drive through three time changes in a couple of hours.
You've got a patchwork of exceptions built on exceptions. Now let's talk about this TZDB database Daniel mentioned. What is it, and why does it matter?
The Time Zone Database — TZDB, sometimes called the Olson database after its founder Arthur David Olson — is essentially the world's shared reference for what time it is anywhere. It maps every region of the world to its time zone rules, including historical changes. When a country decides to change its daylight saving dates, or when a new time zone is created, someone has to update TZDB. Every Linux system, every Android phone, most embedded devices, a huge portion of the internet's infrastructure — they all pull from this database.
It's maintained by volunteers?
A small group. Paul Eggert, a computer scientist at U. , has been the primary maintainer for years. The database lives on a server at the Internet Corporation for Assigned Names and Numbers — I. — but the actual work is done by a handful of people. When Egypt decided to cancel daylight saving time in twenty-sixteen with four days' notice, someone had to rush an update. When Volgograd switched from Moscow time to Moscow plus one in twenty-eighteen, someone had to file a patch. The database contains rules going back to the nineteenth century, and it has to handle things like "this region observed daylight saving from nineteen forty-two to nineteen forty-five, except for this one year when they didn't.
This is the kind of thing where if the maintainers all got hit by the same bus, civilization wouldn't collapse, but a lot of things would get weird.
There have been lawsuits. In twenty eleven, a company called Astrolabe sued Olson and Eggert, claiming the database's historical time zone data infringed on their copyright. The lawsuit was eventually dropped, but it raised a real question: can you copyright facts about when the sun rises? The database is now in the public domain, but the legal uncertainty around it was a genuine threat to internet infrastructure for a while.
We've got this fragile, volunteer-maintained system that underpins global timekeeping. That brings us to the controversies around daylight saving. What does the evidence actually say about whether it's useful?
The evidence is, to put it mildly, not in daylight saving's favor. The original justification was energy savings. But modern studies show the effect is negligible or even negative. A famous study from Indiana in two thousand eight — when the state finally adopted daylight saving statewide — found that residential electricity usage actually increased by about one percent. The extra cooling costs in the evening outweighed any savings from reduced lighting. A Department of Energy report in two thousand eight found a roughly zero point five percent reduction in total electricity use, but that was contested and the methodology had issues.
The health effects? I've seen headlines about heart attacks spiking after the spring transition.
That's real. A Swedish study published in the New England Journal of Medicine in two thousand eight found a roughly five percent increase in heart attacks in the first three weekdays after the spring transition. The fall transition showed a slight decrease, but not enough to offset the spring increase. There's also a documented increase in car accidents. A study from the University of Colorado in twenty twenty found a six percent increase in fatal traffic accidents in the week after the spring transition. Sleep disruption is the mechanism — losing an hour of sleep has measurable effects on attention, reaction time, and cardiovascular stress.
Six percent more fatal accidents. That's not a rounding error. So if the evidence is this bad, why is it still around?
The retail industry and the golf industry have historically been big supporters. More daylight in the evening means more people shopping and more people on the golf course. The National Association of Convenience Stores has lobbied to extend daylight saving. The barbecue industry — this is a real thing — the barbecue industry association has testified in favor of daylight saving because longer evenings mean more grilling. On the flip side, the agricultural sector has historically opposed it, which surprises people. Farmers don't like it because livestock don't care what the clock says. Cows want to be milked at the same solar time regardless. The idea that daylight saving was for farmers is a complete myth — farmers lobbied against it from the start.
The barbecue lobby versus the cows. This is the political economy of time. What about the proposal to just abolish the switch and stay on daylight saving permanently? I know the Senate passed something like that a few years ago.
The Sunshine Protection Act. Passed the Senate unanimously in March twenty twenty-two, then died in the House. It would have made daylight saving permanent, meaning we'd stay on summer time year-round. actually tried this once before — in nineteen seventy-four, during the energy crisis, Nixon signed a bill for year-round daylight saving. It was wildly popular at first, with something like seventy-nine percent approval in December. Then January hit. People realized that permanent daylight saving meant the sun wouldn't rise until after eight a.in much of the country. Kids were standing at bus stops in pitch darkness. There were news reports of children being hit by cars. The approval rating dropped to forty-two percent by February, and Congress repealed it in October nineteen seventy-four, after less than a year.
The objection came from parents who didn't want their kids waiting for the bus in the dark. That's a hard political problem to solve.
It's a real one. If you're in Michigan or Montana in January, permanent daylight saving means sunrise at nine a.That's not an abstract concern. The counterargument is that permanent standard time — the winter clock — gives you earlier sunrises year-round, which aligns better with human circadian biology. The American Academy of Sleep Medicine issued a position statement in twenty twenty calling for abolishing seasonal time changes and adopting permanent standard time, precisely because standard time better aligns with our natural sleep-wake cycles.
The sleep scientists want permanent standard time, the barbecue lobby and the golf industry want permanent daylight saving, and the rest of us just want the switching to stop. That brings us to Daniel's most interesting question — what if we just abolished time zones entirely? One global time, everyone adjusts their schedules instead of their clocks.
This idea has a name — it's sometimes called Universal Time or Single Time Zone. The most famous implementation attempt was Swatch Internet Time in nineteen ninety-eight. Swatch, the Swiss watch company, proposed dividing the day into one thousand "beats," each lasting one minute and twenty-six point four seconds. No time zones, no daylight saving. The reference point was Biel Mean Time, which was just Central European Time, and Swatch's headquarters were in Biel, Switzerland. It was clever marketing, but it never caught on outside of some niche online communities.
A watch company proposing a new global time standard based on their own headquarters' time zone. That's either brilliant marketing or staggering hubris.
But the underlying idea isn't crazy. China already does this — the entire country operates on Beijing time, even though geographically it spans five time zones. In Xinjiang, in the far west, solar noon can be as late as three p.The Uighur population often uses an unofficial local time that's two hours behind, but all official business runs on Beijing time. It works, but it creates a weird split reality where people have two different clocks in their heads.
If you're in western China and your boss schedules a meeting for nine a., that could be what feels like seven a.But everyone adapts.
Right, and that's the argument for a single global time. If the whole world ran on UTC, a meeting at fourteen hundred hours means the same absolute moment everywhere. The question is whether your local working hours shift. In New York, the workday might run from thirteen hundred to twenty-one hundred UTC. In Tokyo, it might be zero hundred to zero eight hundred. The numbers are different, but the solar reality is the same. The advantage is that nobody ever has to calculate time zone offsets again. The disadvantage is that the number on the clock no longer tells you anything about where the sun is.
That's the deeper question — how much do we want the clock to be a solar instrument versus a coordination instrument? Right now, we've got a hybrid system that does both poorly.
That's the core tension. The word "o'clock" literally means "of the clock" — it's an abbreviation of "of the clock" that emerged in the seventeenth century when mechanical clocks started replacing sundials. Before that, people used canonical hours, which were tied to prayer times and varied with the seasons. The idea that an hour is always sixty minutes regardless of season is a mechanical clock invention. So we've already abstracted time away from the sun once before. A single global time zone would just be the next step in that abstraction.
There's something viscerally satisfying about noon being when the sun is roughly overhead. It feels like reality is properly calibrated.
That feeling has real economic and social weight. There's a reason the French held onto the Paris meridian for twenty-seven years. Time is political. When Samoa skipped December thirtieth, twenty eleven entirely — they jumped from December twenty-ninth to December thirty-first to switch from the east side of the international date line to the west — they did it to align their business week with Australia and New Zealand instead of the United States. It was an economic decision dressed up as a calendar trick. You lose a day, but you gain better trading hours.
They just deleted a day from the calendar. Did anyone celebrate a birthday on December thirtieth that year?
If you were born on December thirtieth, you simply didn't have a birthday in twenty eleven. The country of Kiribati did something even more dramatic in nineteen ninety-four. They moved the international date line so that the entire country would be on the same day. Before that, the eastern islands were a day behind the western islands. The president at the time realized that Kiribati would be the first country to see the new millennium if they were all on the same side of the date line. So they bent the line. They literally redrew the international date line for tourism and political bragging rights.
Time isn't a physical thing we're measuring. It's a political agreement that we pretend is a physical thing.
And that brings us to the UTC versus GMT clarification Daniel wanted. GMT is a time zone — the time zone of the United Kingdom during winter. UTC is not a time zone. It's a time standard, defined by atomic clocks, and it doesn't observe daylight saving. The difference is subtle but important. GMT can drift slightly because it's tied to the Earth's rotation, which is irregular. UTC is kept within zero point nine seconds of Universal Time by adding leap seconds when needed. So when people say "UTC is the same as GMT," they're wrong in a precise technical sense — UTC is the atomic successor to GMT, but it's not the same thing.
Don't get me started on leap seconds. That's a whole other episode.
It really is, but briefly — leap seconds are inserted because the Earth's rotation is gradually slowing down, and without them, noon would eventually drift away from solar noon. Since nineteen seventy-two, there have been twenty-seven leap seconds added. The last one was added on December thirty-first, twenty sixteen. And there's a major push to abolish them because they cause software bugs. Google uses something called a "leap smear" where they spread the extra second over a full day to avoid a sudden jump. When you're running a global cloud infrastructure, a sudden extra second can cause cascading failures.
Google is smoothing out time itself to prevent their servers from crashing. That's an incredible sentence. Let's pull this back to Daniel's practical question — what would actually change if we abolished daylight saving tomorrow?
It depends on which version we pick. If we go to permanent standard time, the biggest change is that summer evenings get darker earlier. In New York in June, sunset would be around seven fifteen p.instead of eight fifteen. If we go to permanent daylight saving, winter mornings get darker later — sunrise after eight a.across much of the country. The evidence suggests permanent standard time is better for health, but permanent daylight saving is more popular politically because people like evening light.
The single global time zone idea?
It's technically elegant but socially unlikely. The cost of switching would be enormous — every piece of software, every sign, every schedule, every cultural assumption about what "nine a.China did it because of strong central government authority, and even there, unofficial local times persist. The more realistic path is what we're already doing: gradually reducing the number of time zones through consolidation, and gradually reducing the number of daylight saving transitions. voted to abolish daylight saving in twenty nineteen, but member states haven't agreed on whether to stay on summer or winter time, so it's stuck.
Even when everyone agrees the current system is bad, they can't agree on which replacement is worse.
That's the political economy of time in a nutshell. Everyone hates the switch, but the switch persists because the coalition against it can't agree on the alternative. It's a classic coordination problem. And that's why the TZDB maintainers will probably have job security for decades to come — every time a country changes its mind, someone has to push an update.
And now: Hilbert's daily fun fact.
The average cumulus cloud weighs approximately one point one million pounds — about the same as one hundred elephants. Despite this, it floats because the weight is spread across millions of tiny water droplets dispersed over a vast volume of air that's even denser below it.
What can listeners actually do with all this? First, if you're running Linux or maintaining any kind of server infrastructure, know that TZDB exists and make sure your systems are pulling updates. When Egypt canceled daylight saving with four days' notice, a lot of people found out because their phones were wrong. Second, if you're in a position to influence workplace scheduling, the flexible hours approach Daniel hinted at is worth considering. Instead of arguing about what the clock says, argue about when people actually need to be available. The technology for asynchronous work already exists — the main barrier is cultural.
Third, if you're in the U., your congressional representatives have probably already heard from the barbecue lobby about daylight saving. They could stand to hear from you too. The Sunshine Protection Act keeps getting reintroduced, and whether you want permanent standard time or permanent daylight saving, the research is clear that the switch itself causes real harm. The heart attack data, the traffic fatality data — these aren't abstract statistics. They're people who died because we collectively decided to shift an hour of daylight around.
The big open question for me is whether the single time zone idea gets more traction as remote work spreads. If your team is distributed across eight time zones anyway, the local meaning of "nine a." already breaks down. At some point, the coordination benefits of a single reference time might outweigh the cultural attachment to solar noon. We're not there yet, but the trend lines point in that direction.
If it happens, some future version of the TZDB will have to encode the entire history of time zone transitions so that historians can figure out what time something actually happened. The database already goes back to the nineteenth century. In a hundred years, it'll have to explain the whole chaotic story we just told.
Thanks to our producer Hilbert Flumingtop. This has been My Weird Prompts. You can find every episode at myweirdprompts dot com. For Corn and Herman Poppleberry, I'm Corn. Thanks for listening.
