The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: John Cowan <cowan@ccil.org>
To: segaloco <segaloco@protonmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Dave Cutler recollection about Xenix
Date: Fri, 20 Oct 2023 22:27:59 -0400	[thread overview]
Message-ID: <CAD2gp_QVzZcmGSQd8e1S0Tw-YOuJ8cEhvXe+qnjW=Jst8FVc1A@mail.gmail.com> (raw)
In-Reply-To: <oZOTsmhpK0clmOyHjcgnyIxo-uEyQGpp7lgd6xAXsvMAeK_Xg5YBOUwr3uKqBap7QwAn2yjANeFoNPFB1edpu1JmZ1ZPkdLVTyX48RbyM_4=@protonmail.com>

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

On Fri, Oct 20, 2023 at 8:37 PM segaloco via TUHS <tuhs@tuhs.org> wrote:

 I wonder to what degree that sort of paradigm shift lead to what we see
> today with "app stores" and cheap little apps being peddled a dime a
> dozen.  Must be a viable enough business model if people keep doing it, but
> it makes me die inside.
>

Book publishers made similar complaints about the mass-market paperback
when Robert de Graaf introduced them to the U.S. market in 1939, just in
time for World War II.  They cost about an eighth of the price of the same
book in hard covers and they sold like crazy — 1.5 million in the first
year alone.  Yes, the quality was crap (those early paperbacks are
collectibles now because most of them have fallen apart), but the words
sold books to a huge untapped market who would never have bought a book
before.

Bought any hardbacks lately?

Was it not wanting to have any licensing questions by avoiding anything
> that smelled like Xenix at all?  Or was the consumer base at the time that
> invested in the MSDOS environment that handing them a Bourne shell with
> some ubiquitous UNIX tools would've just been unworkable?
>

I think both of those are pretty likely explanations.  Another possibility
is that the idea was just out of the box for them.  DOS was for one market
and Xenix was for another.

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

  parent reply	other threads:[~2023-10-21  2:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-20 23:27 [TUHS] " Skip Tavakkolian
2023-10-21  0:36 ` [TUHS] " segaloco via TUHS
2023-10-21  0:53   ` Steve Nickolas
2023-10-21  1:04     ` Jim Geist
2023-10-21  2:29       ` Dave Horsfall
2023-10-21  2:27   ` John Cowan [this message]
2023-10-21  6:27 ` Greg 'groggy' Lehey
2023-10-21  7:11   ` steve jenkin
2023-10-21 18:21 ` Stuff Received
2023-10-21 15:36 Paul Ruizendaal
2023-10-21 16:38 ` segaloco via TUHS
2023-10-21 16:40 ` John Cowan
2023-10-24  7:58   ` Sebastien F4GRX
2023-10-22 16:44 ` Paul Winalski
2023-10-22 16:56   ` Jim Geist

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='CAD2gp_QVzZcmGSQd8e1S0Tw-YOuJ8cEhvXe+qnjW=Jst8FVc1A@mail.gmail.com' \
    --to=cowan@ccil.org \
    --cc=segaloco@protonmail.com \
    --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).