From: khm@sciops.net (Kurt H Maier)
Subject: [TUHS] OT: Grace Hopper, Unix epoch, ARPAnet converted to TCP/IP
Date: Sun, 31 Dec 2017 16:59:07 -0800 [thread overview]
Message-ID: <20180101005907.GB6542@wopr> (raw)
In-Reply-To: <alpine.BSF.2.21.1801011056290.99776@aneurin.horsfall.org>
On Mon, Jan 01, 2018 at 11:15:19AM +1100, Dave Horsfall wrote:
>
> My "on this day" policy is to use the local time if it can be narrowed to
> a particular zone where the event happened (and if it makes sense); if it
> was universal e.g. moon landings then I'll use UTC; otherwise I'll use the
> commonly-observed date e.g. the start/end of the world wars.
I support your policy, but I'd say the ARPA in ARPANET makes it at least
feasible to stick with Zulu time for related milestones.
> I'm open to suggestions (including FOAD, in which case I'll simply find
> something better to do).
Personally, I've enjoyed your posts marking anniversaries of these
events.
> A lingering gripe that explains my latent anti-Americanism goes back to
The older I get, the more convinced I am that the "two hard things in
Computer Science" quote came from someone who never had to accurately
report the ages of events predating epoch time.
And I can say as a patriotic American, I did not truly understand the
desperate plight of being a foreigner until I was in Cape Town during
the Super Bowl. After that I limited international travel to extremely
profitable endeavors; otherwise the ROI just isn't there.
khm
next prev parent reply other threads:[~2018-01-01 0:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-31 23:10 Noel Chiappa
2017-12-31 23:22 ` Dave Horsfall
2017-12-31 23:47 ` Kurt H Maier
2018-01-01 0:15 ` Dave Horsfall
2018-01-01 0:59 ` Kurt H Maier [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-01-01 12:59 Noel Chiappa
2018-01-02 0:57 ` Ron Natalie
2018-01-02 16:19 ` Clem Cole
2017-12-31 22:51 Dave Horsfall
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=20180101005907.GB6542@wopr \
--to=khm@sciops.net \
/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).