▲ 1347 ▼ 13 Months (startrek.website) submitted 2 years ago by The_Picard_Maneuver@startrek.website to c/memes@sopuli.xyz 226 comments fedilink hide all child comments
[–] datelmd5sum@lemmy.world 5 points 2 years ago (2 children) Aren't the definitions just a client side issue these days? When times are compared it's unix or unix msec. permalink fedilink source parent hideshow 4 child comments replies: [–] skullgiver@popplesburger.hilciferous.nl 3 points 2 years ago* (last edited 2 years ago) (1 child) [This comment has been deleted by an automated system] permalink fedilink source parent hideshow 2 child comments replies: [–] psud@aussie.zone 4 points 2 years ago 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 permalink fedilink source parent [–] aksdb@feddit.de 1 point 2 years ago Not everything can be done client side. Sending notifications or emails: server side. Basically anything that's automated. permalink fedilink source parent
[–] skullgiver@popplesburger.hilciferous.nl 3 points 2 years ago* (last edited 2 years ago) (1 child) [This comment has been deleted by an automated system] permalink fedilink source parent hideshow 2 child comments replies: [–] psud@aussie.zone 4 points 2 years ago 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 permalink fedilink source parent
[–] psud@aussie.zone 4 points 2 years ago 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 permalink fedilink source parent
[–] aksdb@feddit.de 1 point 2 years ago Not everything can be done client side. Sending notifications or emails: server side. Basically anything that's automated. permalink fedilink source parent
