News for hackers. Stuff that matters.
Re:It’s time to leave the leap second in the past by staticassertion on Monday July 25, 2022 @07:44PM (#32232459)
Yeah how ever will they live with having to wake up slightly earlier or later for their entire lives.
Re:It’s time to leave the leap second in the past by gmiller123456 on Monday July 25, 2022 @09:54PM (#32233363)
So what is it about a system where everyone and every business adjusts their schedule slightly (I guess independently) of each other that is better than the leap second system we have now. Which, as I said earlier, is essentially the same thing, but done in a standardized way.
Re:It’s time to leave the leap second in the past by naniwaduni on Monday July 25, 2022 @10:55PM (#32233729)
Timekeeping at the abstraction level where business hours exist is a lot more tolerant of 40 seconds of error than at the abstraction level where timekeeping primitives are implemented.
Re:It’s time to leave the leap second in the past by mulmen on Monday July 25, 2022 @08:14PM (#32232695)
> earlier or later

My understanding was that leap seconds are only ever added. It’s not like this averages out over time. The problem is that because they are only added the effect is cumulative and eventually some future generation will be eating lunch at 00:00:00.

Re:It’s time to leave the leap second in the past by Nekhrimah on Monday July 25, 2022 @08:50PM (#32232963)
There is a provision for negative leap seconds. In practice, this has never happened.
Re:It’s time to leave the leap second in the past by elfchief on Wednesday July 27, 2022 @03:17PM (#32255352)
Hasn't happened, but it may actually happen in the next half-decade or so. If not, it's almost guaranteed to happen ~25 years from now.
Re:It’s time to leave the leap second in the past by mulmen on Monday July 25, 2022 @08:56PM (#32233006)
Thanks, I skimmed the wiki and it sounded like they could only be added.