I feel like we aren't calling the 2038 problem the "epocholypse" often enough
We should all try harder to make this a thing
I feel like we aren't calling the 2038 problem the "epocholypse" often enough
We should all try harder to make this a thing
What happens in 2038?
@joshbressers why? By 2038, the only 16-bit machines in action will be "Retro". Even IoT devices are migrating to 64 bits - including 64-bit daytime structs.
@lxo the only 32 bit machines you can buy (new) today are IoT (like ESP32, Arduino, etc) and for most of them, handling a date is not something of importance. All x86 currently available (new) are x86_64/amd64. Intel only manufactures 32-bit CPUs for embedded systems and AMD doesn't do 32-bit at all.
Generally, when writing for an embedded system, it is YOUR responsibility to handle data correctness - not the OS'.
@lxo There is no GPS in there, and even if there was, it would have rolled over at least several times by now. It has a rollover period of 19.6 years. The firewall is 64-bit already and it is also such a low-cost item that your argument doesn't even hold water using those. You are seeing dragons and ghosts where there are only gusts and shadows.
@lxo no, you're not. I'm saying there won't be any major problems. I'm also saying that if you purchase today expensive equipment without taking into account the possible issues that can arise wrt you planning to use it past its recommended lifetime, much of the responsibility lies on YOUR shoulders.
But you just be you and keep yelling at clowds. I'm old enough to remeberber Y2K and its non-issues. Linux already proven that Y2K38 is solvable in software.
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.