Some people make a big deal about special dates such as 2000-01-01 or 2011-11-11. Many people, for instance, choose these more "unique" days to get married, even though the day may not fall on a weekend. One example is 2007-07-07 - a summer day that was very popular.
This comic, however, points out that every date is equally unique.
The Mayans had a repeating circle of years, which made it very difficult to record the dates of events far into the past as a given date was not unique! To prevent this, the ISO 8601 states that the Gregorian calendar should be used (i.e. our system), which has no limit on years - but "only" uses four digit years.
Cueball thinks that it is interesting that we have an infinite number of years; it never starts over again. This means that today's date will never be applicable again. It is one of his many hobbies to point this out every day. This would be incredibly annoying to Megan and everyone else!
10th March is an important day though; it's my birthday! - JamesD. 126.96.36.199, 15:58, 17 July 2019 (UTC)
Does nobody realize that March 10th is Mario Day? When you abbreviate march it looks like Mario (MAR10). So, there in fact, is something special about this day. :) 188.8.131.52 20:59, 11 March 2018 (UTC)
What about Daylight Saving Time adjustments and leap seconds? Don't they bring duplicates of the same time or is there a way to account for that in the current system? --Muskar (talk) 10:06, 28 March 2014 (UTC)
- One hour is duplicated each year at the end of DST. Not much happens during that hour, because it's the middle of the night. A poorly written computer program that instructs the computer to set back the clock one hour whenever the clock reaches a specific time would get caught in a recursive loop (never advancing beyond that time). Properly, clocks are set back one hour when that time is first reached, but are allowed to advance after the duplicate hour concludes.
- Not sure if this in regards to a now missing statement in the Wiki, but the reference in the comic is to days. DST occurs as 2AM, so the day is not repeated. However, 1 - 2 is repeated when time is turned back and 2:01 to 2:59 are ignored when moving ahead. Of course, this assumes one lives in a state that recognizes DST. 15:07, 5 October 2014 (UTC)
- Exactly. That's right, Jacky720 just signed this (talk | contribs) 09:56, 14 March 2017 (UTC)
- In Brazil, when we leave DST, we adjust our clocks from 00:00 to 23:00, so there's a chance the day is repeated. 184.108.40.206 04:38, 27 February 2015 (UTC)
Leap second does not result in a duplicate. The additional second is allowed by increasing the number of seconds in a minute. Normally, the 60 seconds of 11:59 are numbered from 11:59:00 to 11:59:59, which is followed by 12:00:00. When there is a leap second, 11:59 has 61 seconds, numbered from 11:59:00 to 11:59:60 (61 total seconds) and then 11:59:60 is followed by 12:00:00.173.245.48.24 18:42, 29 March 2014 (UTC)
My first thought was that he makes fun of people that consider dates like the 12.12.12 as important. As any other date they occur only once and are thus not more special. 220.127.116.11 04:37, 10 March 2014 (UTC)
- Good point, I have added something about that. 18.104.22.168 04:49, 10 March 2014 (UTC)
Possibly related to the upcoming Pi Day. Also, next year's Pi Day will be 03-14-(20)15, which a few images going around on the Internet have made an annoyingly big deal about. 22.214.171.124 06:24, 10 March 2014 (UTC)
So - Maybe I suck at searching (I do), but I can't find any information about us being limited to 4 digits in our calendar system...?126.96.36.199 08:38, 10 March 2014 (UTC)
- Most of the computer software that handles dates would have problems with more (or less) than four digits. Why bother with variable year length when you can just take the first four characters of "2014-03-10" and it works for the next 8 thousand years? 188.8.131.52 09:42, 10 March 2014 (UTC)
- Also, most digital displays are limited to four digits for the year. 184.108.40.206 09:43, 10 March 2014 (UTC)
- And I don't think we actually start address that sooner that in September 9999. It will be Y2K over again! .... not sure where will people of 9999 get Fortran and Cobol programmers, though. Maybe we should freeze some before we run out of them. :-) -- Hkmaly (talk) 10:20, 10 March 2014 (UTC)
- Check this out.--Rael (talk) 21:38, 10 March 2014 (UTC)
- I'm with you. I suppose there may be places where leading zeros are used (somewhere in software where memory space has been set aside, I suppose) but I can't think of any common system where one has to use five digits when using a four digit number.
- When we get to December 31, 9999 (assuming he Gregorian calendar is still in use (BIG assumption)) the next day will simply be January 1, 10000 because, as you said, the Gregorian calendar isn't limited to four-digit years. And, as I say, anyone who think there is some problem with writing years as four digit numbers is simply demonstrating that they are not someone to take seriously. 220.127.116.11 16:32, 10 March 2014 (UTC)
After visiting the website for the "Long Now Foundation", I find I'm left wondering - why, oh why, would they stop at using a five digit year? why not six? eight? ten? sixteen? thirty-two? Brettpeirce (talk) 12:06, 10 March 2014 (UTC)
I think the point in the comic title is that writing years always with 5 digits is as significant as the zero to the left it will take to do so for most of the next 8000 years. FlavianusEP (talk) 12:25, 10 March 2014 (UTC)
My first thought was that the comic was about date formats and yyyy-mm-dd being better than yy-mm-dd or dd.mm.yy. 18.104.22.168 12:40, 10 March 2014 (UTC)
- It isn't, but I've made a dynamic one (based on UTC): https://voidptr.de/xkcd-1340 n.st (talk) 19:36, 12 March 2014 (UTC)
Wanna bet that this comic always shows the current date?--Henke37 (talk) 10:23, 10 March 2014 (UTC)
- Haha, that's a great observation! I wish it were so, I'll check again tomorrow. If it's not, someone email Mr. Munroe to make it so, great idea. -- Adityarajbhatt (talk) (please sign your comments with ~~~~)
- It's 00:07 (11th of March) right now in China where I am currently located and it still shows 10th of March...just for the record 22.214.171.124 16:13, 10 March 2014 (UTC)
- It's March 15th now, and it still says the 10th. It's not dynamic. 126.96.36.199 20:47, 15 March 2014 (UTC)
- It says 2014-10-01 for me. But I think it was at 11:53 (2014-09-30) when I checked it. And mine matches the atomic clock.
188.8.131.52 04:02, 1 October 2014 (UTC)
It's funny that Randall seems to have never heard of RFC 2550, which goes than the Long Now Foundation in expanding the representable date range. 184.108.40.206 15:05, 10 March 2014 (UTC)
- Technically, there will be another 2014-03-10; on October 3rd. - 220.127.116.11 16:01, 10 March 2014 (UTC)
- It would actually be 2014-10-03 "under our system" as stated in the comic. Technically. 18.104.22.168 17:14, 10 March 2014 (UTC)
- It's like me saying that there will be another 2014-03-10 on March 14th. 22.214.171.124 19:45, 10 March 2014 (UTC)
I wonder if this is also somehow related to the Interesting number paradox. 126.96.36.199 18:48, 10 March 2014 (UTC)
The problem of the date rolling back is partially mitigated by storing the year as an integer instead of as characters, such as how certain Spreadsheet programs, such as OpenOffice Calc, stores years as a 16-bit signed integer. This doesn't solve the issue, only pushing it back to be the year 32768 problem. This is even less of an issue for 64 bit Unix time, which expire on 15:30:08 UTC on Sun, 4 December 292,277,026,596. It's also important to note that the dates, such as 99, or 00 should not be seen as digits, they should be seen as characters (unless, of course, they are BCD digits, which entirely defeats the purpose of shortening the date to 2 characters length). This might seem trivial, but I think it's an important difference.188.8.131.52 02:46, 11 March 2014 (UTC)
- 3rd of October won't happen for another seven months. 184.108.40.206 (talk) (please sign your comments with ~~~~)
- As a (culturally) dd/mm/[yy]yy person (and ignoring, for brevity, the different options for delimiter), I find yyyy-dd-mm as illogical as mm/dd/yyyy... Why should anybody switch 'precision direction', mid-way? Still, as someone who went through the Y2K process and worked with colleagues across the Atlantic, I tend to use dd/Mmm/yyyy habitually in "for humans" systems (giving the abbreviated month spelling to avoid all ambiguity, as well as full year-number), or my own "yyyymmdd[-hhmm[ss[.ddd...]]]" format in (informal and internal) programming situations, with comments attached to any conversion routines (inwards and outwards). ((And, yes, there are ISO/other standards, but I find converting from/to them and internally working with my own long-practiced format works best, for me. YMMV. But be aware of how'd you deal with (or ignore) Leap Seconds!)) 220.127.116.11 14:58, 12 March 2014 (UTC)
- I once toyed with the notation 0y20140310, with the "0y" prefix (a pun on C's "0x") distinguishing it from the eight-digit integer 20140310. I later decided that 0y20140310.175959 would be a good way to extend it to specify both date and time, and it still parses as a single C token if that property is useful. (And it sorts properly, of course.) 18.104.22.168 04:15, 24 March 2014 (UTC)
I am surprised nobody has mentioned the fact that we know of no civilization of human beings that has reached 10,000 years with a continuous calendar.Seebert (talk) 14:15, 11 June 2014 (UTC)
We should be doing universal coding for the year. All dates start with a 1, followed by the number of zeroes equal to the number of digits in the number of digits in the date. Take 2015, it has 4 digits, 4 has 1 digit, so it starts with "10" then append the number of digits in the date, "4" and finally the date "2015" to get "1042015". In 8000 years this would be "10510015" in 1e10 years it would be "100101000002015". A computer drops the one, checks the number of leading zeroes, reads in that many digits, then reads in that result in digits to read in the year. With the leading 1 it can still be stored as a binary number rather than a string, and needs no starting or ending indicators, and will expand indefinately to store any date ever to exist. --22.214.171.124 21:22, 20 May 2015 (UTC)
- I just had to add a 'bravo' for whomever appended the  to the "Since time only moves forward" part of the explanation. It makes me happy. Thank you, stranger. - DavidM. 126.96.36.199 06:27, 26 December 2017 (UTC)
- As someone who just nearly choked on his lunchtime sandwich, I second this. Hawthorn (talk) 13:24, 18 March 2019 (UTC)
The Long Now people would have done better to make 2014 12014 (instead of 02014). That way the last 10000 years BCE would become postive numbers as the first 10000 years of the Long Now. This would include all of recorded history as well as, probably, prehistory back to before all of the earliest cities and towns. 188.8.131.52 02:08, 22 October 2020 (UTC)
I know this is a few years late, but it probably should be noted that Before Christ (or Before Common Era for those of you that get hung up on that sort of thing), years were expressed by the establishment of rulers (Year of Rameses, Year of Xerxes, etc.), so in old times you actually did have repeating years.