That’s easy. The 2038 problem is fixed by using 64-bit processors running 64-bit applications. Just about everything built in the last 15 years has already got the fix
Using that fix, the problem doesn’t come up again for about 300 billion years
You don’t need 64 bit programs or CPUs to fix the 2038 problem. You just need to use a 64 bit time_t. It will work fine on 32 bit CPUs or even 8 bit microcontrollers.
There are plenty of smaller devices still running 32-bit ARM processors. Enough of them in fact that Ubuntu 24.04 got entirely recompiled to only use 64-bit timestamps even on 32-bit platforms since by the time it’s out of support 2038 will be less than 5 years away.
hopefully by then it’ll all be sorted by whatever fix they implemented before 2038.
That’s easy. The 2038 problem is fixed by using 64-bit processors running 64-bit applications. Just about everything built in the last 15 years has already got the fix
Using that fix, the problem doesn’t come up again for about 300 billion years
You don’t need 64 bit programs or CPUs to fix the 2038 problem. You just need to use a 64 bit time_t. It will work fine on 32 bit CPUs or even 8 bit microcontrollers.
True, that should have occurred to me. That’s what I get for not touching a compiler since the Christmas holidays started
You mean regular PCs? Sure…
Less COTS stuff? Not necessarily.
There are plenty of smaller devices still running 32-bit ARM processors. Enough of them in fact that Ubuntu 24.04 got entirely recompiled to only use 64-bit timestamps even on 32-bit platforms since by the time it’s out of support 2038 will be less than 5 years away.
Ah, but what about the frontend?