The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: John Gilmore <gnu@toad.com>
To: Clem Cole <clemc@ccc.com>
Cc: The Unix Heritage Society mailing list <tuhs@tuhs.org>
Subject: Re: [TUHS] Troff to ps
Date: Wed, 27 Jan 2021 19:19:59 -0800	[thread overview]
Message-ID: <30778.1611803999@hop.toad.com> (raw)
In-Reply-To: <CAC20D2NCJEhfB5NgaigE8URTKuCqjUtr4nxtrnm4P9Fg3YQ2fA@mail.gmail.com>

Clem Cole <clemc@ccc.com> wrote:
> Actually  It was very cheap. $5 a copy if I remember correctly

We may both be right.  The AT&T license to sell binary copies of UNIX
might have cost Sun only $5 per copy.  Microsoft's Xenix license was
similar; it probably got down to $1 or 50c per copy.  The price per copy
went steeply down as you sold more copies; the licenses soaked the small
sellers and catered to the large volume sellers.  After all, it cost
AT&T *nothing* for a company to sell twice or ten times as many copies;
they weren't supporting the software anyway.

As I recall, when Microsoft supplied the OS for the TRS-80 Model 16,
they blew the doors off all the tiers in their UNIX license.  The 16B
sold 40,000 copies in 1984 (according to Wikipedia), making it the
highest volume UNIX computer of the year.  Clueless monopolist business
people at AT&T had never anticipated that ANYBODY would sell 40,000
copies of UNIX.  Remember when IBM estimated in 1943, "I think there is
a world market for maybe five computers" and DEC in 1977 said "There is
no reason anyone would want a computer in their home"?  See:

  https://www.pcworld.com/article/155984/worst_tech_predictions.html

After the first few years, Sun was shipping high volumes of UNIX systems
(tens or hundreds of thousands per year).  For many years they didn't
need any of the later USL licenses, because they shipped a BSD UNIX that
they were maintaining themselves, and that was (in many peoples'
opinions) higher quality software than anything that USL was offering.
The licensing for the ancient 32V license they needed was written back
in the days when shipping 100 copies was a big deal, so the prices at
the 1,000 or 10,000 or 100,000 copy tiers were very cheap.  Adding 1c to
ship ditroff rather than troff might have been reasonable, but not $5!

	John

  parent reply	other threads:[~2021-01-28  3:20 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-26 14:56 Will Senn
2020-07-26 15:31 ` arnold
2020-07-26 15:35   ` arnold
2020-07-26 16:15     ` Clem Cole
2020-07-26 17:11       ` arnold
2020-07-26 18:03         ` Clem Cole
2021-01-27  5:24           ` Greg A. Woods
2021-01-28  0:19             ` John Gilmore
2021-01-28  1:25               ` Clem Cole
2021-01-28  1:59                 ` Larry McVoy
2021-01-28  3:19                 ` John Gilmore [this message]
2021-01-28 12:58                 ` Clem Cole
2020-07-26 19:05   ` Nemo Nusquam
2020-07-26 22:39     ` Noel Hunt
2020-07-27  5:31     ` arnold
2020-07-27  9:19       ` Jaap Akkerhuis
2020-07-27 11:07         ` Brad Spencer
2020-07-27 15:58   ` Will Senn
2020-07-26 15:33 ` Clem Cole
2020-07-27 15:53   ` Will Senn
2020-07-26 18:09 ` Al Kossow
2020-07-26 23:37 Norman Wilson
2020-07-27 15:08 ` Jaap Akkerhuis
2020-07-28 11:33 Doug McIlroy

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=30778.1611803999@hop.toad.com \
    --to=gnu@toad.com \
    --cc=clemc@ccc.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).