From: stephen@sprunk.org   
      
   On 18-Jun-14 23:33, Adam H. Kerman wrote:   
   > Stephen Sprunk  wrote:   
   >> On 17-Jun-14 13:08, mroberds@att.net wrote:   
   >>> Personally I think using a 24-hour clock would be a better idea,   
   >>> but I realize that's a much bigger change in the world than just   
   >>> printing some new train schedules.   
   >>   
   >> Indeed.  I keep my clocks, phone, etc. on 24-hour time because   
   >> it's easier for me to do timezone math that way (I work with people   
   >> all over the world), but it confuses the heck out of most other   
   >> Merkins unless they've been in the military.   
   >   
   > Wow. That statement makes no sense. Subtraction and addition work   
   > the same way with 12 or 24 hour clocks. One may have to compensate   
   > for two different calendar days, which 24 hour clocks don't help   
   > with.   
      
   But when I add 10.5 hours to 08:00, the result doesn't overflow, and I   
   don't have to wonder whether it's AM or PM.   
      
   Yes, I still have to deal with overflowing a 24-hour clock for meetings   
   in (my) evening, but I still don't have to wonder about AM vs PM.   
      
   > If it's really that much trouble for you, clearly you should simplify   
   > the time zone choice you use and keep your clocks on Greenwich time.   
      
   Unfortunately, the rest of the world doesn't, so I still have to   
   translate into local time zones for _other_ people.  And having   
   "midnight" in my afternoon would be weird.   
      
   S   
      
   --   
   Stephen Sprunk         "God does not play dice."  --Albert Einstein   
   CCIE #3723         "God is an inveterate gambler, and He throws the   
   K5SSS        dice at every possible opportunity." --Stephen Hawking   
      
   --- SoupGate/W32 v1.03   
    * Origin: LiveWire BBS -=*=- UseNet FTN Gateway (1:2320/1)