Kayn@dormi.zone to Programmer Humor@lemmy.ml · 11 months agoJavaScript's days are numbereddormi.zoneimagemessage-square20fedilinkarrow-up1394arrow-down16file-text
arrow-up1388arrow-down1imageJavaScript's days are numbereddormi.zoneKayn@dormi.zone to Programmer Humor@lemmy.ml · 11 months agomessage-square20fedilinkfile-text
minus-squareMystikIncarnate@lemmy.calinkfedilinkEnglisharrow-up33·11 months agoI’m still thinking about the 2037 problem.
minus-squarekvadd@lemmy.worldlinkfedilinkarrow-up25·11 months agoNot to be that guy, but it is the 2038 problem for 32 bit epoch. Check this out: https://en.m.wikipedia.org/wiki/Year_2038_problem But yeah, that’s a much bigger issue.
minus-squareStarDreamer@lemmy.blahaj.zonelinkfedilinkEnglisharrow-up19·11 months agoNo, the 2037 problem is fixing the Y2k38 problem in 2037. Before that there’s no problem :)
minus-squarevsh@lemm.eelinkfedilinkEnglisharrow-up2arrow-down2·11 months agoThis problem is now so old that hardware running it in 2038 will be obsolete
I’m still thinking about the 2037 problem.
Not to be that guy, but it is the 2038 problem for 32 bit epoch. Check this out: https://en.m.wikipedia.org/wiki/Year_2038_problem
But yeah, that’s a much bigger issue.
No, the 2037 problem is fixing the Y2k38 problem in 2037.
Before that there’s no problem :)
right, my bad.
2038*
This problem is now so old that hardware running it in 2038 will be obsolete