US
"add one day to current TAI time"
Size: a a a
2020 May 14
US
hmm, although it should be trivial if you're using TAI with the ISO calendar...
AL
Here’s how I see it:
it’s kinda like TZData. A leap second is added every few years, and it is known in adwance when it will be added. So, right now there’s a 37 second difference between UTC and TAI. So, my hypothetical JS module would have a constant 37 to know that if two dates that I make calculations for are in 2020 I would move by 37.
If dates are in 2017, I would use 36.
So, in general it would be a lookup table inside the module, and the module would make appropriate calculations based on that table.
If a new leap second is announced (they pre-announce it 6 months before) I would expand the table and release an update.
it’s kinda like TZData. A leap second is added every few years, and it is known in adwance when it will be added. So, right now there’s a 37 second difference between UTC and TAI. So, my hypothetical JS module would have a constant 37 to know that if two dates that I make calculations for are in 2020 I would move by 37.
If dates are in 2017, I would use 36.
So, in general it would be a lookup table inside the module, and the module would make appropriate calculations based on that table.
If a new leap second is announced (they pre-announce it 6 months before) I would expand the table and release an update.
SR
там началось если что
ML
там началось если что
ты будешь?
SR
буду скоро, но не долго наверное
SR
чисто пару хамовников с паласатиком
ML
понимаю
EL
ух какая лютая хрень Метаспейс от XP
SR
у них норм на экспериментальных хмелях щас
2020 May 15
EL
а вот 80 офигенное. как будто конфетку из Му-Му ешь
AS
а вот 80 офигенное. как будто конфетку из Му-Му ешь
Правда? Теперь желаю отведать!
FL
А потом копипастой на городские камеры 🙃
SR
крутой ui