Recent searches
Search options
Administered by:
@tridral@toot.wales@drahardja I had a similar experience. I started work at Cardiff University in 1999. Everyone wasooking at systems there and fixing two-digit year problems. We got it done and, of course, 'nothing happened'.
It was called a 'millennium bug' but really it's a century problem. So I'm wondering if we will have the same problem in 2099/2100.
@tridral @drahardja 2099 maybe not, I think we somehow learned our lesson when it comes to the decimal representation.
Unix and related on the other hand didn't, and just slightly increased the bitsize of time_t each time it became problematic and we're getting some Y2038 issues already with dates set in the future but it's going to be such a mess when it'll roll over.
See: https://en.wikipedia.org/wiki/Year_2038_problem
Unix and related on the other hand didn't, and just slightly increased the bitsize of time_t each time it became problematic and we're getting some Y2038 issues already with dates set in the future but it's going to be such a mess when it'll roll over.
See: https://en.wikipedia.org/wiki/Year_2038_problem
en.wikipedia.orgYear 2038 problem - Wikipedia
@lanodan @drahardja Thanks. I'd forgotten all about 2038. I'm glad there are people looking into it.