Kayn@dormi.zone to Programmer Humor@lemmy.ml · 1 year agoJavaScript's days are numbereddormi.zoneimagemessage-square22fedilinkarrow-up1367arrow-down16file-textcross-posted to: programmer_humor@programming.dev
arrow-up1361arrow-down1imageJavaScript's days are numbereddormi.zoneKayn@dormi.zone to Programmer Humor@lemmy.ml · 1 year agomessage-square22fedilinkfile-textcross-posted to: programmer_humor@programming.dev
minus-squareMystikIncarnate@lemmy.calinkfedilinkEnglisharrow-up30·1 year agoI’m still thinking about the 2037 problem.
minus-squarekvadd@lemmy.worldlinkfedilinkarrow-up24·1 year 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-up18·1 year agoNo, the 2037 problem is fixing the Y2k38 problem in 2037. Before that there’s no problem :)
minus-squarevsh@lemm.eelinkfedilinkEnglisharrow-up2arrow-down2·1 year 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