Re:Forebruary, an endless wall calendar
by freehunter on Thursday August 01, 2013 @03:17PM
(#6142766)
Every Intro to CS class could take a week out of their syllabus as suddenly the assignment "create a calendar application that takes input as dd/mm/yyyy and prints the day of the week" disappears from textbook.
Although it would be quickly replaced with "create a calendar app to translate between Gregorian and Modern calendars."
Re:Forebruary, an endless wall calendar
by saidajigumi on Thursday August 01, 2013 @04:04PM
(#6143104)
Which would be a terrible idea. Delivering actual software is all about understanding the real-world problem domain, with all of the complexities inherent to it. Doing a "nerd normalization" of the calendar instead of teaching students how to model and deal with the existing one is pretty much exactly the wrong pedagogical approach.
Re:Forebruary, an endless wall calendar
by icebraining on Thursday August 01, 2013 @05:30PM
(#6143668)
The point would be that the "existing one" itself would change. Many countries adopted the current calendar less than a hundred years ago.
It's a shame nobody had the idea in 1582. Since they were tweaking the Julian calendar, they could have been a bit bolder.
We already are on a "new" calendar system.
If you're on unix/linux/os x, run
cal 9 1752To quote Eliezer, "not every change is an improvement but every improvement is a change". I think people in general are too conservative, and that's why we get stuck for tens or even hundreds of years with suboptimal solutions that are barely good enough to work.
Would it really be a big pain? It's not like you have memorized the calendar. You always look it up, you will just be looking it up in a new system (or not needing to look it up as it's a logical system).
People tend to write date code themselves, no matter how many times we tell them not to.
There have been leap year bugs in everything from Zune to Windows Phone 8 to iPhone/iOS.
This, in spite of legions of CS professors trying to get it into people's heads that they should be using libraries (once, of course, they have verified that said library is accurate).
The pain of moving to a new calendar system would be considerably bigger than the pain of dealing with the current system.