Live data from Hacker News

Australia/Lord_Howe is the weirdest timezone

ssoready.com

51–60 of 466 posts

Re: Australia/Lord_Howe is the weirdest timezone

#51

I find it slightly ironic that a blog that’s educating (and entertaining) us on time and timezones does not itself mention when its blogposts were published, at least on mobile. This one appears to have been published in the summer of 2024.

Seems like pretty timeless content to me.

Re: Australia/Lord_Howe is the weirdest timezone

#52
> With a “designator” time that doesn’t mean much

This might not 'mean much' to the computer, but it means a lot to the human. The computer uses it to communicate with the human and the humans between each other. When I arrange a meeting across timezones I will say CET 16.00 or ET3.00PM and they will understand it faster than saying how much offset we are from UCT.

Re: Australia/Lord_Howe is the weirdest timezone

#53
> Btw it’s called UTC (Universal Time Coordinated? huh?) because the same folks who publish UTC also publish UT1, which is UTC sans the leap seconds.

I’m not sure that’s right! According to legend among metrologists I’ve talked to, “UTC” was chosen as a compromise candidate: it makes sense as an acronym in neither English nor French.

Re: Australia/Lord_Howe is the weirdest timezone

#54
I always say that timezones and font rendering are the most sucking problems that developer can encounter. Both have a ton of weird quirks, both implemented differently across various target devices/OSes and require a lot of time and effort to implement reasonably right.

Re: Australia/Lord_Howe is the weirdest timezone

#55
I’ve found the best way to deal with TZ conversions, is to use UTC as a common fulcrum.

I convert the target TZ to UTC, using my local utility, then use my local TZ utility to convert from UTC to local.

But I write iOS software, so I have very solid local tools at hand. It might be more problematic, on, say, a webserver.

On a related note, I wrote this utility[0], some time ago. It uses the TZ map from the TZ Boundary Builder project[1].

[0] https://github.com/LittleGreenViper/LGV_TZ_Lookup

[1] https://github.com/evansiroky/timezone-boundary-builder

Re: Australia/Lord_Howe is the weirdest timezone

#56

Nah, the weirdest time zone is Africa/Addis_Ababa, which nobody in Ethiopia follows. Instead the locals offset the time by 6 hours. So the AM cycle starts at dawn (i.e. 6am), and the PM cycle starts at dusk (i.e. 6pm). https://en.wikipedia.org/wiki/Time_in_Ethiopia

Sounds like it could be a candidate. Any system which can't be expressed in standard software is stranger than every system that can be.

But whether standard software is able to express this system is up to the software, not the system, no? Why is this way of timekeeping weird, apart from the arbitrary decision not to support it?

Re: Australia/Lord_Howe is the weirdest timezone

#57

Nah, the weirdest time zone is Africa/Addis_Ababa, which nobody in Ethiopia follows. Instead the locals offset the time by 6 hours. So the AM cycle starts at dawn (i.e. 6am), and the PM cycle starts at dusk (i.e. 6pm). https://en.wikipedia.org/wiki/Time_in_Ethiopia

Ethiopian Christians have retained many Jewish customs compared to others, so you will also see them observing something like kosher diets. Although dusk is not sunset, it may be the case that they've adapted the cycle from Hebrew calendar observance.

Re: Australia/Lord_Howe is the weirdest timezone

#59
post #46

Nah, the weirdest time zone is Africa/Addis_Ababa, which nobody in Ethiopia follows. Instead the locals offset the time by 6 hours. So the AM cycle starts at dawn (i.e. 6am), and the PM cycle starts at dusk (i.e. 6pm). https://en.wikipedia.org/wiki/Time_in_Ethiopia

And they live 7 years in the past.

They do. So I guess the observed timezone is UTC-61314.

Re: Australia/Lord_Howe is the weirdest timezone

#60

Earlier quoted context omitted.

Sounds like it could be a candidate. Any system which can't be expressed in standard software is stranger than every system that can be.

But whether standard software is able to express this system is up to the software, not the system, no? Why is this way of timekeeping weird, apart from the arbitrary decision not to support it?

The decision to not support it isn't "arbitrary" per se; it's a function of utility vs cost to implement (which a healthy dose of fudge). "Standard software" for timekeeping is far more useful precisely because it is used by far more people.
Post reply on HN