>If I were writing software like you describe I’d want an explicitly zone-agnostic date(time) to represent it.
I would love to see this as a data type (CalendarDate) baked into languages & databases which would prevent you from applying timezone conversions to it.
Re:Parquet: More than just “Turbo CSV”
by reality_inspctr on Thursday April 06, 2023 @04:16PM
(#35473766)
that would be the goal, but it's hard. I went down a long blog-post road about a "clockchain" which includes a way to reconcile zone-less time. tl;dr all time is relative between a minimum of two objects. all but certain there is an elegant way to do it beyond my current thinking.
https://www.seanmcdonald.xyz/p/the-clockchain-protocol-the-l...
cal.com is solving some of these problems with handling of all zones.
It makes a solid distinction between Dates, times, instants, and zone dates/times.
And Instant is a moment in time. Exposed as a UTC time stamp.
Birthdays etc are best expressed as LocalDates. There’s also LocalDateTime for zone-agnostic features.
If I were writing software like you describe I’d want an explicitly zone-agnostic date(time) to represent it.