cm0002@lemmy.world to Programmer Humor@programming.dev · 7 days agoY-10Klemmy.mlexternal-linkmessage-square21fedilinkarrow-up1345arrow-down14cross-posted to: programmerhumor@lemmy.ml
arrow-up1341arrow-down1external-linkY-10Klemmy.mlcm0002@lemmy.world to Programmer Humor@programming.dev · 7 days agomessage-square21fedilinkcross-posted to: programmerhumor@lemmy.ml
minus-squarepimeys@lemmy.nauk.iolinkfedilinkarrow-up21·7 days agoAnd not using 32-bit integers to calculate time. Which is still a thing in many many many codebases written in C or C++…
minus-squareJustEnoughDucks@feddit.nllinkfedilinkarrow-up3·7 days ago32 bit embedded processors us a lot of 32 bit time, though i am not sure if date time libraries in SDKs have been updated to use 64 bit for time.
minus-squarepimeys@lemmy.nauk.iolinkfedilinkarrow-up5·7 days agoLinux kernel updated to 64 bit time quite recently. In 2038 I can guarantee somebody in a very serious business is still using an ancient RHEL and will have issues.
And not using 32-bit integers to calculate time. Which is still a thing in many many many codebases written in C or C++…
32 bit embedded processors us a lot of 32 bit time, though i am not sure if date time libraries in SDKs have been updated to use 64 bit for time.
Linux kernel updated to 64 bit time quite recently. In 2038 I can guarantee somebody in a very serious business is still using an ancient RHEL and will have issues.