Hacker News Reader

Comment by bluedevil2k | Hacker News Reader

And as long as we're discussing "out there" time notations, I'll throw out my support for a calendar system that makes more sense. 12 30-day months with a 5 (or 6) day "Holiday Month" at the end. Adjusting the "week" to be 10 days instead of 7. 3 weeks a month, 9 weeks a quarter, 36 weeks a year. Work 7 of the 10 days in a week would be the same as a 5-day work week (2 more days off a year actually).

View on HN

Maybe, but that ship has sailed. No-one is going to reform this.

There are many problems with time (see http://www.quirksmode.org/blog/archives/2009/04/making_time_...), but the number of hours per day or the number of days per week or month are none of them.

You might be interested in http://en.wikipedia.org/wiki/International_Fixed_Calendar

I remember it still being used at Kodak when I was a kid and my father worked there.

That's what I have in my time system UIT (linked earlier). I renamed the days to nullday, unday, duoday, triday, quadday, pentday, hexday, heptday, octday, nonday. One nice feature is that if I tell you that it's 1st Unday today, you can see immediately that it's the 12 day of the year (since 0th Nullday is the first day of the year).

What you describe sounds a lot like the French Republican Calendar (linked from the See Also section).

I honestly ask why?

Dates would be the same day forever. Financial quarters would be even and easily divided. Never print a new calendar. Etc.

Seems like all the complexity and special casing of the time keeping is moved into the "holiday month" at the end. E.g., Which financial quarter does it belong to? Moreover only 5 or 6 out of the 10 weekdays will occur in the holiday month, then you have to reset to "Monday" again to have a fixed date->day mapping.

Perhaps a start would be not naming months after dead early roman emperors

Reply on news.ycombinator.com