digibutter.nerr lite

As of now, at this very second, we are exactly **six thousand days away** from the Y2K38 Problem; AKA: the Unix Millennium Problem. I find this interesting, but if you don't... **then too bad!** It's not like anything else is going on here anyway. So, if you don't already know, the Y2K38 Problem is when Unix time (the number that is used to keep the time in almost all computer systems) will reach 2^31, (2,147,483,648 seconds after January 1, 1970) on January 19, 2038, 03:14:07 UTC. When this happens, any 32-bit operating system or application that needs to keep track of the current time, uses the standardized Unix time to keep the time, and stores the Unix time as a /signed/ 32-bit integer, will do one of three things: 1. Incorrectly think the time is December 13, 1901, 2. Throw lots of weird errors, or 3. Break completely and no longer turn back on. A better explanation is available here: https://en.wikipedia.org/wiki/Year_2038_problem So, since modern computers are 64-bit, and 2038 is still 16 1/2 years away, then why should you care, right? Well, for these older 32-bit devices, this is a **really** big deal! While it's impossible to predict what will happen to each individual 32-bit device when the time comes, from a technical standpoint, this is a bigger deal than the Year 2000 Problem. The reason being: instead of a 2-digit year overflowing from (19)99 to (19)00, this is going to be the fundamental timekeeping mechanism itself overflowing. Y2K would have been a big problem if it weren't for the programmers who thought ahead and did everything they could to minimize the effects. This time, however, while having known about this problem at least 38 years in advance, and the earliest effects of it having been felt in 2006 (https://en.wikipedia.org/wiki/Year_2038_problem#Early_problems), currently, our best solution is to just completely stop using 32-bit hardware and software before it goes kaput. This brings me to my final point, the types of devices that are really going to be affected by this: Older devices, especially older embedded systems. For example, computers used in militaries, banks, GPS systems, science laboratories, and vehicles such as cars and airplanes are all often in use for years offline, using outdated hardware and software. If nothing is done about these eventually, there's a real possibility that they'll break and stop functioning when the time inevitably comes. Also, this will affect relatively old web servers that aren't actively maintained anymore if they go unupgraded. Thankfully, none of Nintendo's consoles use Unix time. The GameCube, DS line, Wii, and Wii U all count time starting from January 1, 2000 and store the time as an /unsigned/ 32-bit integer, meaning they can all hypothetically count up to the year 2136 before overflowing. However, the Wii and DS only allow you to set the year up to 2050 for some reason. Also, this is a perfect time for me to point out a little-known Easter egg of the Wii: the system calendar ends on the year 2035. While never confirmed by Nintendo, it is believed that 2035 was chosen for the calendar's end year because: 2035 = 20, 3, 5 --> The 20th letter of the English alphabet is T, the 3rd is C, and the 5th is E --> TCE = The Calendar Ends. Alright, rant's over. 'Twas fun. Thanks for attending my Ted Talk. See you guys in another 1000 days. #Hi-Technicaaaal


https://www.shadoosite.tk/images/6K_days.png This is an accurate countdown: http://www.gregnk.com/2038/