The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Douglas McIlroy <douglas.mcilroy@dartmouth.edu>
To: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Documenter's Workbench versions
Date: Tue, 8 Mar 2022 21:06:42 -0500	[thread overview]
Message-ID: <CAKH6PiXBXNt12sKaJ7ud7FQCsgxJxYyAKwv2HhRzErT2Jc-6mg@mail.gmail.com> (raw)

> The Documenter's Workbench is sort of the unsung hero
> of Unix.  It is why Unix exists, Unix was done to write patents and
> troff and the Documenter's Workbench was all about that.

My response along the following lines seems to have gone astray.

The prime reason for Unix was the desire of Ken, Dennis, and Joe
Ossanna to have a pleasant environment for software development.
The fig leaf that got the nod from Multics-burned management was
that an early use would be to develop a "stand-alone" word-processing
system for use in typing pools and secretarial offices. Perhaps they
had in mind "dedicated", as distinct from "stand-alone"; that's
what eventuated in various cases, most notably in the legal/patent
department and in the AT&T CEO's office.

Both those systems were targets of opportunity, not foreseen from the
start. When Unix was up and running on the PDP-11, Joe got wind of
the legal department having installed a commercial word processor.
He went to pitch Unix as an alternative and clinched a trial by
promising to make roff able to number lines by tomorrow in order to
fulfill a patent-office requirement that the commercial system did
not support.

Modems were installed so legal-department secretaries could try the
Research machine. They liked it and Joe's superb customer service.
Soon the legal department got a system of their own. Joe went on to
create nroff and troff. Document preparation became a widespread use
of Unix, but no stand-alone word-processing system was ever undertaken.

Doug

             reply	other threads:[~2022-03-09  2:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-09  2:06 Douglas McIlroy [this message]
2022-03-09  9:41 ` Jaap Akkerhuis
  -- strict thread matches above, loose matches on Subject: below --
2022-03-07  1:02 Kevin Bowling
2022-03-07  2:42 ` Larry McVoy
2022-03-07 13:28 ` Jaap Akkerhuis
2022-03-07 16:55   ` Kevin Bowling
2022-03-10 17:21     ` ozan yigit
2022-03-07 20:57 ` Kevin Bowling
2022-03-09 22:30   ` Andrew Diller
2022-03-10  0:44     ` Kevin Bowling
2022-03-10  2:17       ` Andrew Diller
2022-03-10  1:10   ` Dan Plassche
2022-03-14  0:17     ` Dan Plassche
2022-03-13  5:24 ` Warren Toomey

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=CAKH6PiXBXNt12sKaJ7ud7FQCsgxJxYyAKwv2HhRzErT2Jc-6mg@mail.gmail.com \
    --to=douglas.mcilroy@dartmouth.edu \
    --cc=tuhs@minnie.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).