TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Exploring 120 years of timezones (2021)

95 pointsby colinprince7 months ago

12 comments

taeric7 months ago
This is always a fun discussion, as the reality is the local time makes enough sense for people to just use it. Having to deal with times across the globe is the anomaly, not the norm. Such that it is unsurprising that it is difficult to do.<p>Even more amusing, the time being fixed length days is definitionally not the norm. Is why the Pacific Northwest is miserable right now. Sun is barely up by 8, and largely down by 5 in the evening. Moving the agreed offset for when we should be awake, as we will do in a couple of weeks, does little to help.<p>And I want to double down on how I worded that. I often see it proposed that we should all move to UTC or some such, but just change when working hours are. But, largely, that is exactly what daylight saving&#x27;s time is. Yes, it is couched in silly phrasing of &quot;saving daylight,&quot; but it is functionally the same as everyone agreeing to move school hours by an hour.<p>I will also double down on my silliest of hot takes. With computers in control of most clocks, I think the problem with DST is that it moves everything by an hour. We could, with today&#x27;s technology, move to something where the clock moves +10 minutes for 6 months and then -10 minutes for 6 months every year and nobody would even really notice.
评论 #41843627 未加载
docdeek7 months ago
&gt; In 1900 this dataset of 282 named timezones indicated 220 different offsets (from UTC), and while some of these were integers, (e.g. Europe&#x2F;Prague, Europe&#x2F;Rome), the majority were not - for example Moscow was 2 hours, 30 minutes and 17 seconds ahead.<p>Moscow changed after that to 2 hours, 31 minutes and 19 seconds for a few years before aligning with a ‘whole hour’ timezone. Fascinating - thanks for sharing!
AStonesThrow7 months ago
I just had a huge and surreal argument with Google&#x27;s Gemini about the current time in other time zones.<p>It was Sunday, 10&#x2F;13. I asked what time it was in London:<p><pre><code> It is currently 1:39 PM MST. As GMT timezone is 7 hours behind MST, the current time in London is 6:39 AM GMT on Sunday, October 13, 2024. </code></pre> Well, no, it&#x27;s not.<p>So I started grilling it on simple math (&quot;What is 13:39 plus seven hours&quot;) and the real offsets of the time zones, and it would respond correctly, and then I&#x27;d ask for the current time again, it&#x27;d apologize profusely, and give me some B.S. calculations right on the same line!<p>I started inquiries about other places, like NZ and across the International Date Line, and it was spectacularly wrong. Some places like PDT it was OK. And it was repeatedly getting tripped up and apologizing and immediately supplying the wrong info again.<p>I was not trying to trick it; I was not going into ambiguous situations or half-hour zones. My locale doesn&#x27;t observe DST, but it was clearly adapting for MST vs. DST zones.<p>The other comical thing was that Gemini would sometimes refuse outright to give the current time, referring me to other methods, as if there were some security blocks on that query. But only sometimes!<p>I simply must conclude that time zones are one of the most difficult programming problems. And I don&#x27;t know how LLMs do time&#x2F;date calculations. But Gemini clearly has a long way to go from these simple math confabulations!
评论 #41840529 未加载
romanhn7 months ago
My favorite video about the madness of timezones: <a href="https:&#x2F;&#x2F;youtu.be&#x2F;-5wpm-gesOY" rel="nofollow">https:&#x2F;&#x2F;youtu.be&#x2F;-5wpm-gesOY</a>. Many great examples, but the one that blows my mind is Israelis and Palestinians living in West Bank observing different timezones in the same geographic location.
captn3m07 months ago
Needs a 2021 in the title. I was curious if it took into account the controversial changes in the tzdb from 2021 <a href="https:&#x2F;&#x2F;www.theregister.com&#x2F;2021&#x2F;09&#x2F;28&#x2F;time_zone_database_controversy&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.theregister.com&#x2F;2021&#x2F;09&#x2F;28&#x2F;time_zone_database_co...</a> since those would have changed the pre-1970 data.<p>But the visualisation was made around Jul 2021, so it avoids those changes (but also the more recent ones): <a href="https:&#x2F;&#x2F;github.com&#x2F;colineberhardt&#x2F;timezone-viz">https:&#x2F;&#x2F;github.com&#x2F;colineberhardt&#x2F;timezone-viz</a>
ck27 months ago
we are getting a moon time zone, maybe, eventually, requires international agreement so maybe never<p><a href="https:&#x2F;&#x2F;www.npr.org&#x2F;2024&#x2F;04&#x2F;09&#x2F;1243405460&#x2F;space-news-moon-nasa-time-zone-white-house" rel="nofollow">https:&#x2F;&#x2F;www.npr.org&#x2F;2024&#x2F;04&#x2F;09&#x2F;1243405460&#x2F;space-news-moon-na...</a>
评论 #41838756 未加载
riwsky7 months ago
Celebrating 120 years, plus or minus four hours, of timezones
dang7 months ago
Discussed at the time:<p><i>Exploring 120 Years of Timezones</i> - <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=28537438">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=28537438</a> - Sept 2021 (9 comments)
thecosas7 months ago
Makes my head hurt thinking about long timeframe datasets across geographies and accounting for all of that as these continue to shift.
评论 #41838720 未加载
ape47 months ago
I imagine the Linux timezone database has grown a lot over the years
TypicalHog7 months ago
Timezones are just so, so, so nasty. Why couldn&#x27;t we just somehow make out shit function on UTC or something?
评论 #41843902 未加载
thomasdziedzic7 months ago
posted 2 days ago: <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=41818394">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=41818394</a>
评论 #41838679 未加载
评论 #41836936 未加载