The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Paul Winalski <paul.winalski@gmail.com>
To: Clem Cole <clemc@ccc.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] DEC compilers (was Happy birthday, John Backus!)
Date: Wed, 5 Dec 2018 13:16:45 -0500	[thread overview]
Message-ID: <CABH=_VRyc2tfP46w8Vgc0sCLAJyaq4m4q_1gP=SJfpJry=+3Bw@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2Nh5w7wPMo0s568cToPSBJd7gtcEWdif57wizqV09_CJg@mail.gmail.com>

On 12/5/18, Clem Cole <clemc@ccc.com> wrote:
> I'll never forget Bill Munson's warnings at the 1980 USENIX conference.
>  Munson ran 'TIG' - Telephone Industries Group, in Merrimack, NH - who job
> at DEC was helping their largest customer: AT&T.    Us university types
> were screaming at Bill and team "When is DEC going to 'support' UNIX?" Bill
> got up an cautioned, 'Be careful what you wish/ask us to do.   If we do
> support Unix, we will have to put Fortran, Cobol, and PL/1 on it -- which I
> don't think you really want.'
>
TIG's mission was to insure that DEC gear did what AT&T wanted.  For
Unix this mainly was assisting in ports to new DEC hardware and
writing device drivers.  Their mission was distinctly NOT to develop
anything DEC-specific.  They were obsessively paranoid about
that--they called such things "vendor traps".  Our attitude in the
VAX/VMS languages and software tools group was very different.  We
were all about making VAX/VMS different, and better, in the
marketplace in order to attract customers to our platform.

When DEC officially decided to do their own, fully supported version
of Unix (to be branded Ultrix), things happened exactly as Bill Munson
predicted.  The VAX/VMS languages & tools group started planning for
an orderly port of all of our products to Ultrix.  We got immediate
and fierce push-back from the Ultrix engineering group (formerly TIG).
So we dropped the whole idea.  Only to have to do a panic port of VAX
Fortran a few years later.  Sigh.  The wonder of culture clashes.

It took a long time for the "vendor trap" idea to die in DEC's Unix
group.  Sun and others weren't as prissy when it came to putting their
own extensions into their Unix offerings, and the DEC Unix group
eventually found themselves being considered a trailing-edge offering.

-Paul W.

P.S. - I forgot VAX RPG as one of DEC's language products.  I think it
was VCG-based, but I'm not certain of that.

  reply	other threads:[~2018-12-05 18:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-05 16:24 Paul Winalski
2018-12-05 16:46 ` Paul Winalski
2018-12-05 17:06   ` Warner Losh
2018-12-05 17:58   ` Clem Cole
2018-12-05 18:16     ` Paul Winalski [this message]
2018-12-05 18:26     ` Henry Bent
2018-12-05 18:46       ` Clem Cole
2018-12-05 18:56         ` Lars Brinkhoff
2018-12-05 19:15         ` Paul Winalski
2018-12-05 21:35           ` Arrigo Triulzi
2018-12-07 19:03             ` Paul Winalski
2018-12-05 19:13 Norman Wilson

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='CABH=_VRyc2tfP46w8Vgc0sCLAJyaq4m4q_1gP=SJfpJry=+3Bw@mail.gmail.com' \
    --to=paul.winalski@gmail.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).