News for hackers. Stuff that matters.
Re:NewCalendar – is it too late to fix a Babylonyan mistake?... by pierrebeaucamp on Saturday January 23, 2016 @09:17PM (#10961160)
I'm all in for a calendar reform, but I prefer the Cotsworth plan: https://en.wikipedia.org/wiki/International_Fixed_Calendar
Re:NewCalendar – is it too late to fix a Babylonyan mistake?... by kseistrup on Sunday January 24, 2016 @02:11AM (#10961792)
Re:NewCalendar – is it too late to fix a Babylonyan mistake?... by mappu on Saturday January 23, 2016 @09:07PM (#10961137)
>same algorithm for determining which years are leap years as the Gregorian calendar

It's ridiculous to propose overhauling the calendar without addressing what is IMO one of the most annoying parts about dealing with calendar dates.

Re:NewCalendar – is it too late to fix a Babylonyan mistake?... by whoopdedo on Saturday January 23, 2016 @10:32PM (#10961344)
And what alternative do you have in mind? We could redefine how long a year is. But that would require some tricky orbital engineering and a very large rocket.
Re:NewCalendar – is it too late to fix a Babylonyan mistake?... by mappu on Sunday January 24, 2016 @12:06AM (#10961546)
I don't have a serious suggestion. It would indeed necessarily involve decoupling the calendar year from the seasonal year. Three 487-day "years" lines up with 4x365 + 1 leap day, and the seasons are still regular (over a longer period).
Re:NewCalendar – is it too late to fix a Babylonyan mistake?... by baisong on Sunday January 24, 2016 @11:34AM (#10962953)
Here's a bit less radical calendar reform, to maximize ease of use: http://www.symcal.info/
Re:NewCalendar – is it too late to fix a Babylonyan mistake?... by joaoqalves on Saturday January 23, 2016 @08:30PM (#10961048)
Too much free time, dude :)