News for hackers. Stuff that matters.

A comment on No leap second will be introduced at the end of June 2026. Parent comment

Re:No leap second will be introduced at the end of June 2026 by vmilner on Monday March 09, 2026 @08:39PM (#47317758)
"And so the Y10K problem was born"
[ Parent | on HN ]
Re:No leap second will be introduced at the end of June 2026 by IKnowComputer on Monday March 09, 2026 @09:20PM (#47318049)
I’d better go brush up on my COBOL
[ Parent | on HN ]
Re:No leap second will be introduced at the end of June 2026 by tadfisher on Tuesday March 10, 2026 @01:28AM (#47319382)
Programmer-Archaeologist will be quite a coveted position 300 gigaseconds from now.
[ Parent | on HN ]
Re:No leap second will be introduced at the end of June 2026 by caymanjim on Tuesday March 10, 2026 @01:42AM (#47319448)
I just had a Y10K problem. Customer data was using 9999-12-31 23:59:59 as a placeholder value, and our app crashed converting from the customer's timezone to UTC. I learned that Python datetime can't handle Y10K.
[ Parent | on HN ]