@[email protected] to Programmer [email protected]English • 5 days agoY-10Klemmy.mlimagemessage-square42fedilinkarrow-up1354arrow-down110cross-posted to: [email protected]
arrow-up1344arrow-down1imageY-10Klemmy.ml@[email protected] to Programmer [email protected]English • 5 days agomessage-square42fedilinkcross-posted to: [email protected]
minus-squareZephyrXerolinkEnglish43•5 days agoDon’t worry, we’re not far away from 2038, when 32 bit unix time rolls over 😅
minus-square@lordnikonlinkEnglish15•5 days agoI will be so excited if we make it that far, double if I’m alive to see it.
minus-squareZagorathlinkfedilink21•5 days ago double I hope you’re not storing time in floating point.
minus-square@lordnikonlinkEnglish1•4 days agoThis is correct Unix time is eternal i kinda wished we would change the calendar again 1970 is just as arbitrary as 2024 years ago so why not set the mark at 1970. Tomorrow will be Jan 1st 0055
minus-squareWasPentalivelinkfedilinkEnglish5•4 days ago<Padme mode> Hopefully we are all working on 64 bit dates, right? right? </Padme mode> :^)
minus-square@[email protected]linkfedilinkEnglish1•3 days agoA surprising number of embedded devices (you know, the ones controlling machinery in factories and stuff) are still running 32-bit processors.
minus-squareWasPentalivelinkfedilinkEnglish1•3 days agoBut you can still do 64 bit math on a 32 bit processor, if you have a carry/borrow flag.
minus-square@[email protected]linkfedilinkEnglish5•4 days agoWhat, and miss out on all the overtime pay from fixing everything at the last minute?
Don’t worry, we’re not far away from 2038, when 32 bit unix time rolls over 😅
I will be so excited if we make it that far, double if I’m alive to see it.
I hope you’re not storing time in floating point.
The Y9999.999999871K bug
We won’t be around, but Unix time will be.
This is correct Unix time is eternal i kinda wished we would change the calendar again 1970 is just as arbitrary as 2024 years ago so why not set the mark at 1970. Tomorrow will be Jan 1st 0055
<Padme mode> Hopefully we are all working on 64 bit dates, right? right? </Padme mode> :^)
A surprising number of embedded devices (you know, the ones controlling machinery in factories and stuff) are still running 32-bit processors.
But you can still do 64 bit math on a 32 bit processor, if you have a carry/borrow flag.
What, and miss out on all the overtime pay from fixing everything at the last minute?