UltraGiGaGigantic@lemmy.ml to Programmer Humor@lemmy.mlEnglish · 4 months agoY-10Klemmy.mlexternal-linkmessage-square41fedilinkarrow-up13arrow-down10cross-posted to: programmer_humor@programming.dev
arrow-up13arrow-down1external-linkY-10Klemmy.mlUltraGiGaGigantic@lemmy.ml to Programmer Humor@lemmy.mlEnglish · 4 months agomessage-square41fedilinkcross-posted to: programmer_humor@programming.dev
minus-squarelordnikon@lemmy.worldlinkfedilinkEnglisharrow-up0·4 months agoI will be so excited if we make it that far, double if I’m alive to see it.
minus-squarejackeryjoo@lemmy.worldlinkfedilinkEnglisharrow-up0·4 months agoWe won’t be around, but Unix time will be.
minus-squarelordnikon@lemmy.worldlinkfedilinkEnglisharrow-up0·4 months 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-squareZagorath@aussie.zonelinkfedilinkarrow-up0·4 months ago double I hope you’re not storing time in floating point.
I will be so excited if we make it that far, double if I’m alive to see it.
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
I hope you’re not storing time in floating point.
The Y9999.999999871K bug