The second is broken: Difference between revisions
No edit summary |
No edit summary |
||
Line 8: | Line 8: | ||
"At Meta, we’re supporting an industry effort to stop future introductions of leap seconds and . . . we believe it is time to introduce new technologies to replace it." | "At Meta, we’re supporting an industry effort to stop future introductions of leap seconds and . . . we believe it is time to introduce new technologies to replace it." | ||
"At best, such a time jump crashed programs or even corrupted data, due to weird timestamps in the data storage." | |||
"The impact of a negative leap second has never been tested on a large scale; it could have a devastating effect on the software relying on timers or schedulers." | |||
"In any case, every leap second is a major source of pain for people who manage hardware infrastructures." | |||
</blockquote> | </blockquote> |
Revision as of 17:45, 27 December 2023
JULY 25, 2022 |
It’s time to leave the leap second in the past
|