14 ms·
Insane complexity of calendrically correct date and time operations
- vortico 8y agoIs it true that Unix time is as simple as it seems? Is there exactly one second between adjacent integers? Do all Unix time values occur only once simultaneously around the world?
- aidenn0 8y agoNo, because unix times can repeat in the case of leap-seconds (this is necessary to be able to represent future times correctly).
- ushi 8y agoWhat you want is probably TAI [1], Unix Time has leap seconds. [1] https://en.wikipedia.org/wiki/International_Atomic_Time https://en.wikipedia.org/wiki/International_Atomic_Time
- vortico 8y agoThanks! That's what I was looking for.
- petre 8y agoOr GPS time which is UTC w/o the leap seconds
- Tor3 8y agoThe one mistake with UNIX is that UTC is used. It should have been TAI, and leap second adjustment should have been handled by the timezone package (but at the time people weren't worried about leap seconds, so it's understandable). As it is, the system clock has to change. This is as bad as MSDOS time (and other systems which put localtime into the actual RTC). Using UTC as the time reference, independent of local time, was nearly genius. With TAI it would have been pure genious. No, wait, using an epoch time of the Big Bang, and step size Planck time, now that would have been pure genious. It doesn't take as many bits as you may think..
- zokier 8y agoFrankly I'm bit confused why civil time in general is based on UTC instead of TAI. Except for astronomy, who does benefit from observing leap seconds?
- bloak 8y agoCivil timekeeping is based on UTC because we want clocks and calendars to remain synchronised with the sun. It's not just astronomers who care about whether the sun is above the horizon. If you think about it, the solar day is the one unit of time that almost everybody cares about and pays attention to. If you screw up the day, you also screw up the week and anything else that is based on counting days. Why would you want to do that?
- repolfx 8y agoBut offset of UTC for TAI is like 37 seconds or something poxy like that. Nobody cares about this, the sun moves too slowly for that to make any difference. There's been talk of setting UTC=TAI for quite a long time and I think it'd make sense. It'd take so long for TAI to drift from the actual rising and setting of the sun that we'd probably all have standardised on Swatch Beats by then anyway.
- bloak 8y agoYes, the difference is 37 seconds now, but it's growing quadratically. It's quite possible that we'll change the way we express times and dates, but it's almost certain that we'll want them to stay in phase with the sun, and we'll probably want to stick with the SI second and with something like TAI. My guess is we'll continue to want a simple relationship between TAI (or its successor) and the civil clock time, something like the current relationship according to which they are a whole number of seconds apart. That implies that we'll need something like leap seconds (or leap minutes perhaps). There doesn't seem to be a reasonable alternative.
- blattimwind 8y agoUnix time depends on the wall clock time, so it is a wall clock time, so it can jump around arbitrarily when the computer clock is adjusted, and its seconds can be stretched as needed for gliding adjustments. Applications need to cope with that.
- JdeBP 8y agoIt depends from the Unix and decisions by the local system administrator. * https://unix.stackexchange.com/a/327403/5132 https://unix.stackexchange.com/a/327403/5132
- deleted 8y ago[deleted]
- yboris 8y agoThe Problem with Time & Timezones - Computerphile https://www.youtube.com/watch?v=-5wpm-gesOY https://www.youtube.com/watch?v=-5wpm-gesOY A fantastic overview of the headaches you'd have if you wanted to code all this.
- jchw 8y agoMany of these make the weird assumption that you want to support multiple calendars. For better or worse, this is rarely the case.
- projektir 8y agoYes, or that you care about historical aspects. If we go on a far enough time scale, all calendars are constructed abstractions so theoretically nothing about them is true, but I'm not sure what's the point of that.
- xenadu02 8y agoI think that's a bit naive. Properly supporting calendrical calculations serves two major purposes: 1. Serve the billions of people who don't use the Gregorian calendar or who live in areas that don't match your idea of time zones. 2. Functions as a human form of "platform independence". Properly handling dates/times quickly exposes places you've made silly assumptions or accidentally broken things. This protects you from actual bugs and ensures you avoid whatever the future version of the Y2K problem is. Such bugs are always easier to fix when you have a smaller database and fewer users.* * In general bugs and breaking changes _never_ get easier. Every day you delay increases the pain imposed on future you and users. Obviously there is a balance - a startup needs to worry about getting to "default alive" first and foremost - but don't delay too long and where it doesn't impose an inordinate cost do it right the first time.
- jchw 8y agoI didn't say you would Never want to support multiple calendars, but like I said. For better or worse, most software written will not.
- nitwit005 8y ago> Serve the billions of people who don't use the Gregorian calendar or who live in areas that don't match your idea of time zones. There isn't that much use of non-Gregorian calendars in software, even in places that do make use of them. And if you do support them, it's another source of bugs, as you have to deal with new Japanese era names and the like: https://blogs.msdn.microsoft.com/shawnste/2018/04/12/the-japanese-calendars-y2k-moment/ https://blogs.msdn.microsoft.com/shawnste/2018/04/12/the-jap...
- teddyh 8y agoThis could very well have been called “Falsehoods programmers believe about date and time calculations”. It fits very well into the pattern of other similarly titled lists which have been published in recent years.
- colemannugent 8y agoHere's one such list for anyone interested: https://github.com/kdeldycke/awesome-falsehood https://github.com/kdeldycke/awesome-falsehood
- severine 8y agohttps://infiniteundo.com/post/25326999628/falsehoods-programmers-believe-about-time https://infiniteundo.com/post/25326999628/falsehoods-program... edit: which cites https://infiniteundo.com/post/25326999628/falsehoods-programmers-believe-about-time https://infiniteundo.com/post/25326999628/falsehoods-program... (from HN's own patio11) as inspiration, as the original "Falsehoods programmers believe about X".
- mmt 8y agoI think you meant it cites https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-believe-about-names/ https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-...
- severine 8y agoYou're right, thank you. I missed the edit window.
- Mr_Nippl-e 8y agohttps://www.youtube.com/watch?v=1LopIroSjsU https://www.youtube.com/watch?v=1LopIroSjsU
- lloeki 8y agoThere's a follow-up: https://infiniteundo.com/post/25509354022/more-falsehoods-programmers-believe-about-time https://infiniteundo.com/post/25509354022/more-falsehoods-pr...
- Theodores 8y agoImagine we did not have names for months and days. Would you call the tenth month October or December? It does not make sense. Then, the other months at the start of the calendar, would you name them after phases of a military campaign of preparation for war, conquering, looting and pillaging? Would that be deemed politically correct? On the weekday names we are not doing any better. Tuesday - named after the god of war? Doesn't make sense to me. As for the lengths of the months, imagine if you were trying to make the case for the different lengths of months and you were trying to get buy in from your friends in accounts. Surely they would want equal amounts of days in each quarter? Imagine trying to persuade them that different lengths were better, what plausible possible reason could there be? We learn the names of days and months by rote at a very young age. We get encultured into accepting the status quo and never questioning little details - nobody asks at school why 'Dec'-ember is month twelve.
- nonbel 8y ago>"Then, the other months at the start of the calendar, would you name them after phases of a military campaign of preparation for war, conquering, looting and pillaging?" Do you have a reference for this? Besides Mars how are the others related? And also that would make a lot of sense to name periods of time after what you are doing during that time. Edit: Also, I remember reading that the one thing the pharaohs of ancient egypt had to pledge before taking power was not to change the calendar again. Since changing it according to whatever current whims caused even more chaos. At some point the "deep state" of the time just wouldn't stand for it anymore. Edit2: Found the ref. Actually I mentioned it here a few years ago: "It must have been, then, that there were local attempts to retain the coincidences between the true and the calendar year — intercalation of days or even of months being introduced, now in one place, now in another ; and these attempts, of course, would make confusion worse confounded^ as the months might vary with tlie district, and not with the time of year. That this is what really happened is, no doubt, tlie origin of the stringent oath required of the Pharaohs in after times, to which I shall subsequently refer. [...] When the year of 365 days was established, it was evidently imagined that finality had been reached ; and, mindful of the confusion which, as we have shown, must have resulted from the attempt to keep up a year of 360 days by intercalations, each Egyptian king, on his accession to the throne, bound himself by oath before the priest of Isis, in the temple of Ptah at Memphis, not to intercalate either days or months, but to retain the year of 365 days as established by the Antiqui.^ The text of the Latin translation preserved by Nigidius Figulus cannot be accurately restored; only thus much can be seen with certainty. To retain this year of 365 days, then, became the first law for the king, and, indeed, the Pharaohs thenceforth throughout the Avhole course of Egyptian history adhered to it, in spite of their being subsequently convinced, as we shall see, of its inadequacy." https://archive.org/stream/dawnastronomyas00lockgoog/dawnastronomyas00lockgoog_djvu.txt https://archive.org/stream/dawnastronomyas00lockgoog/dawnast... https://news.ycombinator.com/item?id=11017726#11020076 https://news.ycombinator.com/item?id=11017726#11020076
- NelsonMinar 8y agoThe leap second has a history of breaking computers. Pretty much every Linux server running Java broke in 2012, for example. 2009 saw a bunch of Linux kernels crashing in logging code. 2016 was mostly better except for Cloudflare: their systems had an assumption time never runs backwards. https://blog.cloudflare.com/how-and-why-the-leap-second-affected-cloudflare-dns/ https://blog.cloudflare.com/how-and-why-the-leap-second-affe...
- RcouF1uZ4gsC 8y agoThis is why some Google and AWS smear the leap second. https://developers.google.com/time/smear https://developers.google.com/time/smear https://aws.amazon.com/blogs/aws/look-before-you-leap-the-coming-leap-second-and-aws/ https://aws.amazon.com/blogs/aws/look-before-you-leap-the-co...
- chopin 8y agoImho that's no better. A leap second "smears" the day lengths. Smearing the leap second means introducing changes at some scale, eg. more or less micro- or nanoseconds. Software needs ro be able to cope with this.
- rkagerer 8y agoI had the same thought but... The smear technique results in seconds that are 11.6μs longer than nominal, and Google makes the case this is within the "manufacturing and thermal errors of most machines' quartz oscillators". So at face value, I'd say software already copes with discrepancies of that order. However I would infer the maximum delta actually seen by an NTP client is larger and depends on the client's polling interval. e.g. If a machine runs a normal clock locally and synchronizes every 20 minutes (which is probably on the high side), it would see about a 14ms jump on each sync during the 24 hour smear window. That's assuming the NTP client doesn't already use a smear algorithm locally to correct for drift (Windows doesn't, but I think Red Hat Linux might? Per https://access.redhat.com/solutions/39194 https://access.redhat.com/solutions/39194 "NTP polling does not directly synchronize the local system clock to the server clock; rather, a complex algorithm calculates an adjustment value for each tick of the local system clock") Maybe someone more well-versed can elaborate further.
- hesk 8y agoWhat surprised me the most on that list was the the Unix epoch is December 31, 1969 in Los Angeles.
- rossy 8y agoDon't let that answer confuse you. It seems to be phrased in an intentionally confusing way, but it's really only talking about time zones. At midnight 1970-01-01 UTC, Los Angeles, North America, and roughly half of the world still had their calendars on the previous day, because they have a negative time zone offset (Los Angeles was UTC-8:00).
- ggm 8y agoSummer of love has echoes down the years...
- throw7 8y agoJust learned google calendar uses the timezone your currently in by default even if you set the location back to your home. When I got back from travel, the notification was decidedly off. :)
- Hnrobert42 8y agoGoogle’s “helpful” treatment of time zones decidely isn’t. I wish there was a way to tell google calendar to ifnore timezones altogether. E.g. I am in Vietnam. I make a dentist appointment for when I am back in the US at 2 pm. I put the appointment on the calendar. I get to the US on the day and find the appointment is at 1 am the day before. Worse still, is in the opposite direction because I wont get the alarm until the event has passed by 11 hours. Stop being clever google. If I put an event in my calendar for 2pm, just leave it there. Yes, yes, I could hunt down the timezone menu item every time. Better yet, I finally get around to transitioning out of that terrible company’s services.
- SneakyMission 8y agoFalse. It’s the year 5779 in the Hebrew calendar. שנה טובה
- abraham_lincoln 8y agoשנה טובה
- Lapsa 8y agoprogramming in a nutshell
- nneonneo 8y ago"False. The UNIX epoch is January 1, 1970 in UTC, but is Dec 31, 1969 in Los Angeles." This isn't specific to Los Angeles, right? It's just referring to the fact that anyone with a negative UTC offset would see an epoch date of Dec 31, 1969 in their local time (I hope).
- Eduard 8y agoTrue.
- pm215 8y agoOne related wrinkle that can catch out UK people (who tend to conflate local non-summer-time with UTC) is that the epoch is not midnight 1 Jan 1970 in UK time -- we were in the middle of a "UK time is GMT+1 all year round" experiment in 1970...
- Tor3 8y agoHm. No. The UNIX epoch is in UTC, so it's always January 1, 1970. The tick (at this moment: 1537511644) is always relative to January 1, 1970. The timezone (TZ) only comes into it when that epoch time is translated to a local time with 'date' and other tools.
- ProblemFactory 8y agoYes. This reminds me of an anecdote from a talk on timezones. Shortly after Stephen Hawking died, the the Google search snippet for "When did Stephen Hawking die" said "Tomorrow" for people in the US. It was pulling the date from Wikipedia, but it was still the previous day in the US.
- deleted 8y ago[deleted]
- kuwze 8y agoI’ve heard that Perl 5 has the best/most complete DateTime library. Is that true?
- petre 8y agoIt cares about leap seconds so yes, it's quite accurate.
- drtillberg 8y agoChrist Church College at Oxford still makes a limited use of 'local time' offset 5 minutes and 2 seconds from the time zone. https://greenwichmeantime.com/info/oxford/ https://greenwichmeantime.com/info/oxford/
- josecastillo 8y agoI've encountered just about every item on this list working on my Apple Watch complication, Better Day[1], which supports 11 calendar systems in 21 languages. The funny thing is, the last item on this list — always use ICU through the NSCalendar API — is the exact conclusion I arrived at, and one that I preach to anyone who will listen. Especially with modern Swift syntax, complex questions like "what's the current day of the year" end up having simple, almost poetic answers like "calendar.ordinality(of: .day, in: .year, for: date)". And you can trust that they are correct for every calendar and every locale. Usually. [2] [1] https://itunes.apple.com/us/app/better-day-a-complication/id1052023515?ls=1&mt=8 https://itunes.apple.com/us/app/better-day-a-complication/id... [2] https://www.joeycastillo.com/notes/2016/09/18/of-crescent-moons-and-calendars/ https://www.joeycastillo.com/notes/2016/09/18/of-crescent-mo...
- tewt 8y agoI only skimmed your article, but are you sure that's right? There must have been at least several date adjustments before your app was release yet the system time maintained the correct date. Presumably it'll correct afterwards, invalidating the date offset.
- josecastillo 8y agoThe thing to keep in mind is that before the sighting, the months are pre-calculated for when the first crescent moon should rise over Mecca. So a change only affects the single month where the observation differed. For example, if you're expecting to see the first crescent moons on October 10, November 9 and December 8, but you didn't see the first one until October 11, that doesn't push the moon sightings out for the rest of the year. It just means that the month you thought would end on October 9 will have an extra day, and the month you thought would start on October 10 will start a day later (and as a result will be a day shorter). Future months are still totally fine; the date offset is just a temporary fix that the user remembers to turn on when the announcement is made, and to turn off at the end of the month.
- draw_down 8y agoI really dislike the tone these sort of things tend to take, which is “here’s some stuff you think but you’re wrong about.” The reason people get stuff like this wrong (and names, and addresses, and and and) is because it’s really hard to get right. And it’s added difficulty on top of writing code which is already pretty challenging.
- Semiapies 8y agoEspecially when it's all stuff that's already been covered in very similar essays. Actually introducing good libraries and methods for handling these issues properly would be much more useful than a smug collection of fallacies and a tacked-on link to ICU at the end.
- deleted 8y ago[deleted]
- Tempest1981 8y agoThe main point is “don’t be naive, since it’s more complicated than you think.” Knowing it’s complex, the next step is to get help, not hack up your own solution. I liked the tone... sort of a “can you believe this?!”
- akeck 8y agoFor quick scripts, I do all my date math with seconds-since-the-epoch, retrieved with "date", and then convert back at the end. The final date benefits from the latest timezone package update, so mostly I do OK.
- innocenat 8y agoThis mostly work without problem for past time, but it can be wrong for future time, since timezone/DST may change. When you want 2pm next Sunday, you want 2pm next Sunday local time, not whatever 2pm next Sunday is supposed to be as of now.
- shimon 8y agoAfter I read to the end, I half expected it to load more calendar fallacies.
- eldavido 8y agoThis is actually a lot simpler than it looks. There are two concepts. Calendars almost never have crazy holes in the middle of them. When you say "I'm in Chicago", you pretty much can schedule an appointment at 1 or 2pm on "Sunday" or "9/20" or "next Wednesday" and everybody knows when that will happen. Leap years cause a little bit of trouble. Where it gets tricky is when you have to interact with wall clock times, say, calculating the number of hours until your calendar event happens, or looking for all the events in a given range of wall clock dates. This is the world of timestamps, offsets, and "the global timeline" that everyone in the world experiences together. Calendars also don't really care about daylight saving time. If you keep these two separate and are specific about which you're dealing with, 90% of this goes away. Separate calendar from arithmetic/wall clock times. Not all will disappear, but a surprisingly large amount. Source: working on https://www.interval.org/ https://www.interval.org/ and using the excellent NodaTime library. Thank you, Jon Skeet.
- macintux 8y ago> Calendars almost never have crazy holes in the middle of them. The comment right above yours at the moment talks about effectively that very problem (in this case, an unforeseen date moving a calendar back a day). https://news.ycombinator.com/item?id=18036403 https://news.ycombinator.com/item?id=18036403
- joshu 8y agoYours in calendrical heresy, JS
- MrMorden 8y agoJust as well this article doesn't contain a technique for locally making P=NP. I've never trusted Vidona, and I never will.
- King-Aaron 8y agoI seem to remember Tom Scott doing a really good little video about this.
- ilikehurdles 8y agoThis one: https://www.youtube.com/watch?v=-5wpm-gesOY https://www.youtube.com/watch?v=-5wpm-gesOY
- VeXocide 8y agoHere's my personal favorite, GMT +0h 19m 32.13s, which was used in the Netherlands until July 1, 1937: https://en.wikipedia.org/wiki/UTC%2B00:20 https://en.wikipedia.org/wiki/UTC%2B00:20
- zipwitch 8y agoFrom the list: All the important years are four digits long This left out the Long Now Foundation's advocacy for five-digit years to deal premptively with the Y10K bug. And, less tongue-in-cheek, to promote a view of time that is not conventional in this day and age.
- lxmorj 8y agohttps://www.youtube.com/watch?v=czgOWmtGVGs https://www.youtube.com/watch?v=czgOWmtGVGs
- Zaheer 8y agoReminds me of another great post on the topic by Zach Holman: https://zachholman.com/talk/utc-is-enough-for-everyone-right https://zachholman.com/talk/utc-is-enough-for-everyone-right
- wolfv 8y agoI invented this very regular calendar while I was writing recurring-scheduling software for a scheduling tool: https://calendars.wikia.com/wiki/6*6*10_regular_calendar https://calendars.wikia.com/wiki/6*6*10_regular_calendar It was my fantasy escape from the crazy irregularities of the Gregorian calendar.
- pmontra 8y agoCan you imagine the transition to that calendar? People wanting their two days off every five working days are one of the problems.
- wolfv 8y agoIt will never happen. The US can't even get on the metric system. The UN couldn't even reform the calendar to have uniform quarters: https://en.wikipedia.org/wiki/World_Calendar https://en.wikipedia.org/wiki/World_Calendar http://strangeside.com/time-sabbath-on-tuesday-364-day-year/ http://strangeside.com/time-sabbath-on-tuesday-364-day-year/
- WalterBright 8y agoThis really should be an operating system service, so all the applications get it right. Instead, everybody rolls their own, with erratic results.
- Spivak 8y agoAndroid: https://developer.android.com/reference/android/icu/util/Calendar https://developer.android.com/reference/android/icu/util/Cal... Apple Everything: https://developer.apple.com/documentation/foundation/nscalendar https://developer.apple.com/documentation/foundation/nscalen... CentOS: https://centos.pkgs.org/7/centos-x86_64/icu-50.1.2-15.el7.x86_64.rpm.html https://centos.pkgs.org/7/centos-x86_64/icu-50.1.2-15.el7.x8... Windows: https://docs.microsoft.com/en-us/windows/desktop/intl/international-components-for-unicode--icu- https://docs.microsoft.com/en-us/windows/desktop/intl/intern...
- WalterBright 8y agoOnly Microsoft's seems to be part of the operating system.
- netgusto 8y ago> Weeks start on Sunday in the United States, Monday in Europe, and a couple of places start on Saturday. Wow. I live in Europe, and find it weird that people can consider the week to start on Sunday. I guess everything that may appear normal within a cultural frame of reference can be off in another, even the most basic of things!
- thaumasiotes 8y agoWhat is the relevance of saying that a week starts on a particular day? In the most common usage, the "week" starts on Monday in the United States, and concludes on Friday, to be followed by the "weekend". A calendar week of 7 days does start on Sunday, but who cares? If they changed how the calendars were printed, life would be different in no way.
- NewsAware 8y agoWell for me as Dev it changes how I render a week calendar to a user
- netgusto 8y agoSo for all intents and purposes, the week actually starts on Monday in the US, if I understand what you're saying. For instance, if I were to tell you "Beginning of next week, I'm gonna X", you'd understand Monday, correct?
- thaumasiotes 8y agoIf you said that to me at work, I'd understand Monday, because Sunday is not part of the work week. I'd likely understand it as Monday in other contexts too, because it's very rare for something to start on Sunday. Monday and Saturday are the transition points and thus the logical places to start doing something. But I might understand it as Sunday if context seemed to point that way. What I'm saying is that nothing is organized according to "the beginning of the week", so the question of which day is the beginning of the week doesn't have any implications.
- _ph_ 8y agoBonus problem: in my company, the business calendar (which is the first week of the year, quarter ends) is sometimes shifted by one week with respect to the ISO definitions for historic reasons. I have implemented a large application which does a lot of time calculations, and run onto most of the issues listed in the article, except that I didn't use hewbrew calendars :).
- partycoder 8y ago> Weeks start on Sunday > False. Weeks start on Sunday in the United States, Monday in Europe, and a couple of places start on Saturday. In some countries weeks start on Mondays. > All the important years are four digits long > False. It’s the year Heisei 30 in the Japanese calendar. Or 13.0.5.15.0 in the Maya calendar.
- StreamBright 8y agoThe only question I got is: why we as humans cannot fix this by having a proper calendar system that actually reflects the world and does not have these flaws?
- nandemo 8y agoWhat do you mean by "actually reflecting the world"? If you mean using objective criteria of some sort, how would that help deciding if the week starts on Sunday or Monday, or what days of the week are to be business days?
- pmontra 8y agoThe world is irregular (Earth's rotation and revolution durations vary) but we want regularity in our calendars and clocks. That's the source of the problem.
- acd 8y agoWisdom and experience from senior hacker developer "Oh you are working with time and dates that is going to get "complicated"" Lets propose a new time format we could count the number of exoseconds since the beginning of the universe. Then convert that number to whatever native time format we want. Store that as a number and use that for conversion. Age of universe 4.415×10^17 seconds, 4.415×10^26 exoseconds
- flukus 8y agoNot universal enough, areas near a black hole have experienced less time, the CMB has experience 0 exoseconds, even earth and space will slowly diverge. This will just make a lot of future programmer cyborgs very unhappy.
- JdeBP 8y agoYou are reinventing TAI64NA badly. * http://cr.yp.to/libtai/tai64.html http://cr.yp.to/libtai/tai64.html
- peter303 8y agoA proper programmed petaflop computer should be able to handle this.
- peter303 8y agoChoose a non-Earth-centric time standard. People speculate how a space-faring society would be able to synchronize time and location under relativistic physics. The answer is an intergalactic GPS using far away qusar locations and frequencies. The Voyager probes located Earth for a futrue viewer using a quasar GPS.
- justinjlynn 8y agostill not stable over long time periods unless you account for stellar drift (which gets more and more uncertain over time)
- FrozenVoid 8y agoThe whole problem results from people using the same time for user-display and time calculations. Display time is user-facing feature that Should Not Influence system time. If people used https://en.wikipedia.org/wiki/International_Atomic_Time https://en.wikipedia.org/wiki/International_Atomic_Time for software none of the problems related to calendars will occurs. IAT has no leap seconds or any calendar corrections at all.
- cryogenic_soul 8y agoI think on of the best attempts to fix calendar system was done by George Eastman (Kodak founder), who presented "International Fixed Calendar" created by Moses Cotsworth to League of Nations in 1923. At that time League of Nations was trying to redesign current calendar system and was accepting different proposals. Unfortunately they failed to come to consensus between different calendar designs :( https://en.wikipedia.org/wiki/George_Eastman https://en.wikipedia.org/wiki/George_Eastman https://en.wikipedia.org/wiki/Moses_B._Cotsworth https://en.wikipedia.org/wiki/Moses_B._Cotsworth https://en.wikipedia.org/wiki/International_Fixed_Calendar https://en.wikipedia.org/wiki/International_Fixed_Calendar https://en.wikipedia.org/wiki/International_Fixed_Calendar_League https://en.wikipedia.org/wiki/International_Fixed_Calendar_L... https://gizmodo.com/how-the-quest-for-a-perfectly-rational-calendar-created-1697616634 https://gizmodo.com/how-the-quest-for-a-perfectly-rational-c...
- Asooka 8y agoThat calendar's weeks start on Sunday and I would rather have hours vary by length of daylight throughout the year than start weeks on bloody Sunday.
- Balgair 8y agoAs the ephemeral Tom Scott also demonstrates [0], even IF you account for all the listed factors (and many more) you are STILL sometimes out of sync, just due to the nature of the power grid itself. As Albert said: Time is what clock measure. The more you dig into it, the more you realize how true that is! [0] https://www.youtube.com/watch?v=bij-JjzCa7o https://www.youtube.com/watch?v=bij-JjzCa7o