seaice@lemmy.world to Mildly Infuriating@lemmy.worldEnglish · 1 year agoPublic clockslemmy.worldimagemessage-square37fedilinkarrow-up1202arrow-down112file-text
arrow-up1190arrow-down1imagePublic clockslemmy.worldseaice@lemmy.world to Mildly Infuriating@lemmy.worldEnglish · 1 year agomessage-square37fedilinkfile-text
minus-squareLittle1Lost@feddit.delinkfedilinkEnglisharrow-up4·1 year agoEver heard of the 2048 bug? If no i suggest taking a look at the wikipedia page. I think it is a fun read
minus-squareArrogantAnalyst@feddit.delinkfedilinkEnglisharrow-up4·1 year agoYou mean the Year 2038 problem?
minus-squareLittle1Lost@feddit.delinkfedilinkEnglisharrow-up2·1 year agoyes… i feel dumb for that typo
minus-squareguy_threepwood@kbin.sociallinkfedilinkarrow-up6·1 year ago2038! I develop embedded systems and we’ve been testing for this for years now. There’s also a similar 2036 GPS bug
Ever heard of the 2048 bug? If no i suggest taking a look at the wikipedia page. I think it is a fun read
You mean the Year 2038 problem?
yes… i feel dumb for that typo
2038! I develop embedded systems and we’ve been testing for this for years now. There’s also a similar 2036 GPS bug