The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: George Michaelson <ggm@algebras.org>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Plan 9 from outer space ?
Date: Mon, 20 Apr 2020 13:08:06 +1000	[thread overview]
Message-ID: <CAKr6gn1pv_crfQdT+CcFPqn+xJ6ow06eC12wyeWZw7114m-Y+w@mail.gmail.com> (raw)
In-Reply-To: <CAKzdPgx-XsNTs-UVahCq5oH6rJDD9sGyCedyT+eZDR41_DiNzQ@mail.gmail.com>

Sometimes a cigar is just a cigar, but "ceci, n'est pas un pipe" is
also true: just because you called it a cigar, doesn't mean it can't
be a fish.

The version I heard once, was "hitch the wagon to the engine and see
what entrains" where every one of hitch, wagon, engine, entrain does
not refer in any way to railways, or even "wagons" if its shakespeare.

It is not very useful to try and have a conversation about anything
EXCEPT the mutability of words, if you don't actually agree what the
words mean in context. I think this may be why Haskell draws a
distinction between things of type Integer and the specific intent
behind "int" and I could be drawn to say the whole 8/16/32/64/128
problem inherent in (unsigned (long) ) int is kind-of more of a
problem than not.  If we'd selected IPv6 as 64 bit quantities then
because at the time the 32/64 division of intent was mostly ok, we'd
be good. We went to 128: GCC (sorry) doesn't handle unsigned 128 bit
quantities well. A problem ensues.

On Mon, Apr 20, 2020 at 12:50 PM Rob Pike <robpike@gmail.com> wrote:
>
> A name that refers to something does not imply some form of metempsychosis. Sometimes a cigar is just a cigar.
>
> -rob
>

  reply	other threads:[~2020-04-20  3:08 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-19 14:35 Norman Wilson
2020-04-19 15:59 ` Daniel Camoles
2020-04-19 22:19   ` Rob Pike
2020-04-20  7:42     ` arnold
2020-04-20 17:35       ` Christopher Browne
2020-04-20 20:49         ` Rob Pike
2020-04-23 15:33           ` Álvaro Jurado
2020-04-23 17:10             ` Richard Salz
2020-04-19 23:42 ` A. P. Garcia
2020-04-20  2:27   ` Michael Usher via TUHS
2020-04-20  2:50     ` Rob Pike
2020-04-20  3:08       ` George Michaelson [this message]
2020-04-20  4:39       ` Warner Losh
2020-04-24 20:55   ` Dave Horsfall
  -- strict thread matches above, loose matches on Subject: below --
2020-04-19  3:09 Doug McIlroy
2020-04-18 17:20 Richard Tobin
2020-04-18 17:23 ` Pierre DAVID
2020-04-18 17:44   ` Warner Losh
2020-04-18 17:49     ` Royce Williams
2020-04-18 22:26       ` Rob Pike
     [not found]         ` <CAG=a+rgFs6ZB9X7H=hZnP4thm4r0xP_2c-apfeOEbM936zXkaA@mail.gmail.com>
2020-04-19  1:28           ` Rob Pike
2020-04-19  2:51             ` Adam Thornton
2020-04-18 16:57 Pierre DAVID
2020-04-18 18:40 ` A. P. Garcia
2020-04-18 21:38 ` 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=CAKr6gn1pv_crfQdT+CcFPqn+xJ6ow06eC12wyeWZw7114m-Y+w@mail.gmail.com \
    --to=ggm@algebras.org \
    --cc=tuhs@tuhs.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).