-
Notifications
You must be signed in to change notification settings - Fork 154
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Should Temporal ship a TAI and/or GPS time zone? (or document how to build in a cookbook sample?) #900
Comments
related: #893 |
I think cookbook samples are a good idea, and a separate library (the same kind of thing that @pipobscure mentioned when we were talking about microformat parsing in the last meeting) |
temporal-tai doesn't seem to work, and to be honest I'm not sure what to expect from a "TAI" time zone, given that TAI is basically "more absolute than Absolute" rather than a normal time zone in which calendar dates and times have well-defined meaning. I guess each leap second would introduce a new offset rule such that e.g. Regardless, I very much support adding this to the cookbook. |
Cookbook example to be written after the freeze and before Stage 3 |
On further reflection this isn't a requirement for Stage 3. To be done later. |
While fielding replies to my tweet about https://yourcalendricalfallacyis.com/ , I noticed that @ryzokuken had already built a custom time zone for TAI, which (as I naively understand it) is the same as UTC but without leap seconds. https://github.com/ryzokuken/temporal-tai/blob/master/index.mjs
It seems like a fairly simple implementation. Should Temporal ship with a TAI time zone (or also a GPS time zone?) so folks who want better leap second support can get it without rolling their own?
If not, are these two good candidates for cookbook samples?
BTW, there was already some feedback about this a while ago: #133
I admit I don't know much about leap seconds (@gibson042 knows a lot more) so this may not be a helpful suggestion-- but at least wanted to capture it here.
The text was updated successfully, but these errors were encountered: