The Epochalypse Project
epochalypse-project.org
The Epochalypse Project
1–10 of 91 posts
Re: The Epochalypse Project
#215 years ago i was working at a startup in SV and a kid we hired was saying how he was sad he missed out on y2k because he was too young. I filled him with joy when I mentioned the 2038 bug. lol
Re: The Epochalypse Project
#3(Not) Looking forward to 2038 onwards as people ignore the fact we coordinated to fix this and start saying it was all a big hoax.
Re: The Epochalypse Project
#4The fact that it's not common knowledge and not taught in schools and universities is concerning.
Re: The Epochalypse Project
#5Born too early for Y2K, but just in time for the Epochalypse lol
Re: The Epochalypse Project
#6my capitalist side remembers that many people made retirement money because of Y2K.
Maybe I should start thinking about an early retirement :)
Re: The Epochalypse Project
#7Who will register a domain for the upcoming year 292271025015 problem?
Re: The Epochalypse Project
#8When will milliseconds since the Unix epoch not be precisely representable in IEEE double anymore? (As it's used in JavaScript.)
Re: The Epochalypse Project
#9I think this effort would benefit from trying to qualify what “unpredictable ways” actually means. If anyone is testing devices, a catalog of test results describing the actual failure modes that were revealed would help make this whole thing more concrete.
I think many software engineers know that if you want to make any organization care about this type of issue, you need to be ready to demonstrate the severity and impact.
Re: The Epochalypse Project
#10When will milliseconds since the Unix epoch not be precisely representable in IEEE double anymore? (As it's used in JavaScript.)
In the year 287390 (285420.9 years after 1970) according to my calculations using DuckDuckGo’s calculator.
If you ask ChatGPT it’s:
= 285,616 years after 1970
= Year 285,616