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.
Insane complexity of calendrically correct date and time operations
61–70 of 146 posts
Re: Insane complexity of calendrically correct date and time operations
#62I’ve heard that Perl 5 has the best/most complete DateTime library. Is that true?
Re: Insane complexity of calendrically correct date and time operations
#63From 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.
Re: Insane complexity of calendrically correct date and time operations
#64Is 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?
Re: Insane complexity of calendrically correct date and time operations
#65False. It’s the year 5779 in the Hebrew calendar. שנה טובה
Re: Insane complexity of calendrically correct date and time operations
#66Is 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?
What you want is probably TAI [1], Unix Time has leap seconds. [1] https://en.wikipedia.org/wiki/International_Atomic_Time
Re: Insane complexity of calendrically correct date and time operations
#67Re: Insane complexity of calendrically correct date and time operations
#68https://calendars.wikia.com/wiki/6*6*10_regular_calendar
It was my fantasy escape from the crazy irregularities of the Gregorian calendar.
Re: Insane complexity of calendrically correct date and time operations
#69Re: Insane complexity of calendrically correct date and time operations
#70"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).