2038 is only a problem for systems with 32 bit Unix time timekeeping. Right now that’s only a few embedded systems, in fifteen years there will be even fewer
This isn’t even remotely as bad as Y2K where many systems used two digits to store years and rolled over unpredictably when tested. We considered one system in my workplace “good enough” as it rolled over to 100 so the calculations still worked. Others crashed, for example clobbering something in RAM when adding 99 + 1 and storing the results in two bytes
Aren’t the definitions just a client side issue these days? When times are compared it’s unix or unix msec.
deleted by creator
2038 is only a problem for systems with 32 bit Unix time timekeeping. Right now that’s only a few embedded systems, in fifteen years there will be even fewer
This isn’t even remotely as bad as Y2K where many systems used two digits to store years and rolled over unpredictably when tested. We considered one system in my workplace “good enough” as it rolled over to 100 so the calculations still worked. Others crashed, for example clobbering something in RAM when adding 99 + 1 and storing the results in two bytes
Not everything can be done client side. Sending notifications or emails: server side. Basically anything that’s automated.