The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: norman@oclsc.org (Norman Wilson)
Subject: [TUHS] OT: trains [Was: Date madness]
Date: Mon, 18 Dec 2017 08:03:20 -0500	[thread overview]
Message-ID: <1513602204.10161.for-standards-violators@oclsc.org> (raw)

Ian Zimmerman:

> How do other train systems handle [DST], e.g. the European intercity 
> system?

Dave Horsfall:

  UTC?  It's not hard to get used to it.

=====

You misunderstand the problem.

Suppose I'm planning to board a train at 0300 on the morning
Daylight Time ends.

Now suppose the train actually departs an hour early, at 0200,
because it originated before the time change and some nerd who
never rides trains declared that it shall not wait the extra
hour until scheduled departure time.

Nerds may be happy, but the paying passengers won't be.  Telling
passengers to set their watches to UTC just won't happen.  (Some
of us nerds actually had our watches on GMT for a few months
back in the years that gave the `Nixon table' in old ctime.c
its (informal) name, but gave up because it was just too damn
much work to stay in sync with the real world.)

Once upon a time, before railways had radio communications and
proper track-occupancy signalling, the consequences were more
serious than that: if you run an hour ahead of schedule, you
risk colliding with another train somewhere.  That is why it
was the railways that first accepted and promoted standard time
zones.

Nowadays it's not about scheduling and safety, just about
having an acceptable user interface.

In a similar vein, I know of at least one case in which Amtrak
changed the official departure time of a train (that requires
advance reservations and often runs full) from 0000 to 2359,
because people would get confused about which day midnight
falls on and show up a day late.  (Actually the Amtrak
timetable read 1200 midnight and 11:59 PM, but 24-hour time
is one of the changes I agree people should just accept
and use.)

Norman Wilson
Toronto ON


         reply	other threads:[~2017-12-18 13:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-13 22:16 [TUHS] Date madness Norman Wilson
2017-12-14  0:24 ` Chris Torek
2017-12-17 16:20   ` Ron Natalie
2017-12-17 18:53     ` Tom Ivar Helbekkmo
2017-12-17 20:07       ` Ron Natalie
2017-12-17 21:24         ` [TUHS] OT: trains [Was: Date madness] Ian Zimmerman
2017-12-17 22:35           ` Dave Horsfall
2017-12-18 13:03             ` Norman Wilson [this message]
2017-12-18 16:45               ` Ian Zimmerman
2017-12-19  0:48                 ` Dave Horsfall
2017-12-18 16:12           ` Steve Mynott

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1513602204.10161.for-standards-violators@oclsc.org \
    --to=norman@oclsc.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).