News for hackers. Stuff that matters.
Re:Jiff 1.0: A datetime library for Rust by masklinn on Tuesday November 17, 2026 @04:47AM (#50529385)
> This feels like duplicative work better done in a library.

While not necessarily wrong, it should probably be a separate library entirely: there are projects maintaining GIS boundaries for the IANA timezones.

Re:Jiff 1.0: A datetime library for Rust by kccqzy on Tuesday November 17, 2026 @01:51PM (#50536319)
After some more thought, I agree this should be a separate library. I did some search, and I found that ICU library seems to contain all the timezones in the world and their display names. https://cldr.unicode.org/translation/time-zones-and-city-nam...

I found the icu::TimeZoneNames class. The docstring even describes my exact problem:

> For example, people in the United States refer the zone used by the east part of North America as "Eastern Time". The tz database contains multiple time zones "America/New_York", "America/Detroit", "America/Montreal" and some others that belong to "Eastern Time". However, assigning different display names to these time zones does not make much sense for most of people.

I then looked at the icu::TimeZoneNames::find member function and it seemed to do exactly what I proposed. https://unicode-org.github.io/icu-docs/apidoc/dev/icu4c/clas... Except it’s marked as internal use only. I don’t know what’s going on.