I learned to program in the 1980s. I promise you that for most programs written then the coder was like, “Two digit year, of course. Why waste so many bytes with a four digit year? Nobody will be using this software in 15 years!” And probably 95% of the time they were right….
Comment on What is the deal with IPv6?
slazer2au@lemmy.world 8 hours ago
Because people are slow to fix something unless it is an impending problem.
Take the Y2K bug. Did you know the original person who made the big was telling people in the 70s that is needs fixing? And it wasn’t actually fixed till the second half of the 90s.
2038 is going to be a fun year with all the 32bit clocks overflowing to 1970
iknewitwhenisawit@fedinsfw.app 6 hours ago
palordrolap@fedia.io 8 hours ago
2038 problems have already started happening in niche cases. I expect things will pick up in pace in a couple of years because 10 years is that sort of period of time that people like to post-date future events by.
That might be enough to scare a few of the hold-outs. Then 2033 will be the next scare and reminder, because five years, etc.
Then probably every year after that until the deadline hits. By that point, the remaining few will be using
faketimeor something like it to eke out a few more years from whatever ancient hardware they're still running that is too expensive to replace.Fun fact, and possible hint: Setting the date back 28 years on such hardware could work in a pinch, since the calendar from 2010 to 2037 is identical to that from 2038 to 2065. All weekdays and leap days fall on the same dates. (Easter and other moveable feasts don't, however.)
NeatNit@discuss.tchncs.de 7 hours ago
Actually 13 December 1901, since it overflows to negative, not zero.
Other than that, good answer, full marks
slazer2au@lemmy.world 6 hours ago
Right… signed vs unsigned ints.