RFC 2550 – Y10K and Beyond (1999)

You can already hit these problems today. People always think about the current date, although there very valid are reasons to store future (or past) dates.

For example, if you're are a scientist you might want to calculate where planet xyz is in 100,000 years - and store that date on your computer, today.

Please label this as 1999, April Fool's Day .

We're 16 days behind 1st of April, at the time of this writing...

Also see: http://longnow.org/about/ which aims to fix Y10K/YAK/YXK but unfortunately not Y100K/Y64K/YCK (yet anyway).

It's interesting seeing how Wikidata has been storing dates. They store things like the time that the universe started as a date, which means the year is about 11 digits.

JavaScript's Date object doesn't like such big dates - I don't think it works with anything greater than a few hundred million years.

> A 32-bit counter for the number of seconds since 1970 [UNIX] wraps in 2038.

What's the bet this one actually causes problems