Windows 2000 Posted August 16, 2016 Posted August 16, 2016 (edited) Today I am here to ask an interesting question and put some worries in the head on peoples who aren't aware of the "Problem Of 2038". The clock strikes 03:14:07 UTC on Tuesday, 19th January 2038, a total of 2147483647 seconds since 1st January 1970. You may ask, "Alright, but why do I care that 2147483647 seconds would've passed since 1970 in 19th January 2038?" - Because, 1st January 1970 is the date when the 32 bit count started. The problem is that this 32 bit thingy has a limit of 2147483647 seconds. One great example, of why do we care about this limit is the song "PSY - Gangnam Style". Since YouTube was using that 32 bit system to count views back then, as you may guess there was a bit of a problem once that song reached 2,147,483,647 views. Once it reached 2,147,483,647 views, the YouTube views counter broke. Of course, after this YouTube is now using 64 bit system, which can handle up to 9,223,372,036,854,775,807 views. That's good for YouTube, but what about computers that use 32 bit counting system in 19th January 2038? - According to Google, they will just malfunction but I am also asking this question here, because I am curious if someone of you can at least share a theory or make an attempt to predict!? Edited August 16, 2016 by Windows 2000
jaclaz Posted August 17, 2016 Posted August 17, 2016 It will happen exactly the same thing that happened for the millennium bug: Nothing worth of note, nothing to see, move on people. https://en.wikipedia.org/wiki/Year_2000_problem By 2038 everything will be 64 or 128 bit or maybe 256 bit or possibly 512, with the nice side effect that to store 1 you will use a senselessly long binary, and what the heck, in 20 years times there could be quantum computing, teleports, humanity might evolve in beings of pure light or go back to the stone age, nothing really to worry about. https://en.wikipedia.org/wiki/Year_2038_problem jaclaz
helpdesk98 Posted August 17, 2016 Posted August 17, 2016 as an experiment couldn't you just set a 32bit systems clock to 1 minute before 19th January 2038 and just wait and see what happens? I would test multiple operating systems starting with older ones like 3.1 and 9x systems. I think the clock would just geek out for a minute throwing some sort of invalid system time error lol.
Windows 2000 Posted August 19, 2016 Author Posted August 19, 2016 (edited) On 17.08.2016 г. at 3:59 PM, helpdesk98 said: as an experiment couldn't you just set a 32bit systems clock to 1 minute before 19th January 2038 and just wait and see what happens? I would test multiple operating systems starting with older ones like 3.1 and 9x systems. I think the clock would just geek out for a minute throwing some sort of invalid system time error lol. This is not how these things work... Edited August 19, 2016 by Windows 2000
helpdesk98 Posted August 19, 2016 Posted August 19, 2016 the xmas trees are telling me other wise! just joking of course.
Recommended Posts