Re:It’s time to leave the leap second in the past
by ble on Monday July 25, 2022 @01:50PM
(#32228212)
Is UTC as a system inherently unsafe or does it just expose unwary programmers to bugs, the vast majority of which are somewhere between benign and inconvenient in impact?
Re:It’s time to leave the leap second in the past
by ncmncm on Monday July 25, 2022 @04:30PM
(#32230497)
It generates gratuitous, totally unnecessary bugs with impact wholly unpredictable.
Re:It’s time to leave the leap second in the past
by thrown_22 on Tuesday July 26, 2022 @02:34AM
(#32235092)
If you want a system with no leap seconds use TAI. This is not rocket science. I implemented this in my first real job for a broker trader in 2009 who had exposure in Japan and Australia (leap seconds happen at 10/11am there).
If a 21 year old grad can move 200 terabytes of historical data 15 years ago what are the best and brightest at FB doing with their lives?
Re:It’s time to leave the leap second in the past
by tgv on Monday July 25, 2022 @01:15PM
(#32227600)
> could lead to disastrous results
You mean some influencer's timeline could get messed up? The horror!
Re:It’s time to leave the leap second in the past
by dastbe on Monday July 25, 2022 @02:00PM
(#32228388)
whether you like it or not, people are using facebook (and google, and amazon, and so on) as critical infrastructure.
there are also all the other companies out there who do not have the platform that meta has that can also hit the same issues. i'm sure some of them have products you wouldn't be so glib about.
Re:It’s time to leave the leap second in the past
by mrguyorama on Monday July 25, 2022 @04:06PM
(#32230220)
>whether you like it or not, people are using facebook (and google, and amazon, and so on) as critical infrastructure.
Only facebook here is the one suggesting we should change things, so who is using facebook as critical infra and what is your definition of "critical" here.
even with the best and brightest engineers there is a non-trivial probability that someone will make an assumption that is invalid based on their understanding of what can happen (ex. leap seconds never go negative!) or the library their using (this ensures monotonic time!) that could lead to disastrous results. and especially at meta scale, that probability is no longer "will someone make this mistake in our code?" but is "how many times will people make this mistake in our code?", so systemic solutions that eliminate this as a class of problem an individual can create is something we should consider.