Computer Old Farts Forum
 help / color / mirror / Atom feed
From: Adam Thornton <athornton@gmail.com>
To: Harald Arnesen <skogtun@gmail.com>
Cc: Computer Old Farts Followers <coff@tuhs.org>
Subject: [COFF] Re: Awk, not Kaw?
Date: Mon, 25 Jul 2022 10:36:25 -0700	[thread overview]
Message-ID: <CAP2nic1zb7u3Zuf_ogRha7pTLY=xsC2_X-VKz6Yny34_6QEL4Q@mail.gmail.com> (raw)
In-Reply-To: <1a0f8f01-3a23-46f3-329a-6511e308b4d1@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1413 bytes --]

I mean let's look at this logically.  We only have six possibilities:

AWK: well, it won.  It's easy to pronounce.  It does sound like an extinct
flightless bird, which is helpful in a world in which ORA is going to come
along with its distinctive product line book covers.
AKW: unpronounceable, but probably would have turned into "ak-dub".  Nah.
KWA: I like this one.  But then I'm a fan of Waiting For Godot.
KAW: Well, yeah, the ORA cover would have been a crow.  Just about as good
as AWK, really.
WKA: "wocka wocka" is the noise Pac-man makes.  Unfortunately the program
predated the video game by three years.  Would have been a great ORA cover
though.
WAK: "This language is WAK" would have been excellent marketing.  I'm a
little sorry this one didn't win.

Adam

On Mon, Jul 25, 2022 at 2:49 AM Harald Arnesen <skogtun@gmail.com> wrote:

>
> Dan Cross [25/07/2022 02.33]:
>
> > `akw` seems like the most promising alternative, for
> > no other reason than that the initials are alphabetized.
> > `kaw` feels a bit silly, sounding like the noise that a
> > crow makes.
> >
> > I suspect "awk" was the closest to pronounceable
> > without seeming unduly goofy.
>
> Whether a crow cries "kaw" or "awk" is open to discussion...in
> Norwegian, it says "kra".
>
> I have always thought the name was a play on the bird "auk". The Book
> even has a picture of this creature on the cover.
> --
> Hilsen Harald
>

[-- Attachment #2: Type: text/html, Size: 1993 bytes --]

      reply	other threads:[~2022-07-25 17:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <e9f4cb6a-a382-71a5-8603-1485d9675d30@gmail.com>
2022-07-24 23:30 ` [COFF] " Stuff Received
2022-07-25  0:33   ` [COFF] " Dan Cross
2022-07-25  9:47     ` Harald Arnesen
2022-07-25 17:36       ` Adam Thornton [this message]

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='CAP2nic1zb7u3Zuf_ogRha7pTLY=xsC2_X-VKz6Yny34_6QEL4Q@mail.gmail.com' \
    --to=athornton@gmail.com \
    --cc=coff@tuhs.org \
    --cc=skogtun@gmail.com \
    /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).