• sigil 12 days ago

    We need a catchy, vaguely ominous name to scare people into action. “Y2K38” isn’t cutting it.

    Proposed rebranding: The Epochalypse.

  • rl3 12 days ago

    Why, that sounds negatively epochalyptic.

  • jedberg 12 days ago

    I'll be just over 60 years old when that happens. With any luck, I'll be retired and not have to worry about it... I think having to deal with both Y2K and Y2K38 in one career is too much.

  • dwd 12 days ago

    We're at 72% gone.

    June 10th, 2024 we hit 80%.

    April 1st 2031 - 90%. (maybe not a good day to tell everyone to start worrying)

    August 25th 2034 - 95% (panic time)

    As an aside, I always use 2038-01-19 for any far future end dates rather than a null.

  • runjake 12 days ago

    While we're worrying about the Y2K38 problem, don'r forget to worry about the Year 2036 Problem [1], as well. Here's a pretty good summary of the upcoming time-related fun [2].

    1. https://en.wikipedia.org/wiki/Year_2038_problem#Network_Time...

    2. http://www.lieberbiber.de/2017/03/14/a-look-at-the-year-2036...

  • ryanbertrand 11 days ago

    We launched a crime based RPG game on iOS back in the day that had a leaderboard which tracked in game net worth (cash, investments, etc).

    I still remember the day we woke up to multiple emails and lawsuit threats from our top player whose net worth suddenly went negative on the leaderboard.

    Our players were very competitive and loved pushing the boundaries by trying to find vulnerabilities, shortcuts, etc so we assumed the worst and thought we had a bug in our system! Turned out to be our JSON parsing library was using integerValue on our NSNumber instances causing the ints to overflow. It was a tough week waiting for Apple to review the app while our players lost faith in us.

    Lesson learned :)

    (Luckily the player and our community were understanding and stay around)

  • franzwong 12 days ago

    Japan's emperor will step down this year. They need to change their calendar too.