News for hackers. Stuff that matters.
Re:Time to Dump Time Zones by curun1r on Sunday November 06, 2016 @07:49PM (#12888040)
> eschewing AM/PM in favor of a 24-hour clock

Even if we keep AM/PM, we should make it make sense. It should switch when the numbers roll over. Having 11am be followed by 12pm is nonsensical. The fix for this, as any programmer will tell you, is to recognize that 12 is really 0...we've got an off-by-one bug. Midnight should be 0am and noon should be 0pm.

Re:Time to Dump Time Zones by nayuki on Sunday November 06, 2016 @11:34PM (#12888841)
Yes, this proposal does make things a lot easier because:

twelveHour = twentyFourHour mod 12

But instead with the status quo, we need to add this extra line of logic:

if twelveHour == 0 then twelveHour = 12

Re:Time to Dump Time Zones by colejohnson66 on Monday November 07, 2016 @01:28AM (#12889285)
> But instead with the status quo, we need to add this extra line of logic:

> if twelveHour == 0 then twelveHour = 12

That's because humans naturally begin counting from 1, not 0. Mainly because we are counting objects, not adding an array index to a pointer.

Re:Time to Dump Time Zones by fnj on Monday November 07, 2016 @07:09AM (#12890447)
Time is not a count. Time is a linear displacement, just like distance. As such, it only makes sense to start with 0. Did you ever see a ruler that starts with "1" at the very end? Of course not. It starts with "0", but they just don't bother to print the "0".

One inch is a displacement of "1" from the beginning. One hour is a displacement of "1" from the beginning. It's pretty stupid to arbitrarily call the beginning "12".