The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: kevin.bowling@kev009.com (Kevin Bowling)
Subject: [TUHS] Why did PDPs become so popular?
Date: Wed, 27 Dec 2017 16:38:59 -0700	[thread overview]
Message-ID: <CAK7dMtAoa8bPWrY9z=Ch6_QfH4nJnq-YQpX4WHXFiyVLnLD5gw@mail.gmail.com> (raw)
In-Reply-To: <109152082.5216233.1514413535270@mail.yahoo.com>

I understand IBM systems history a lot better, but it looks
simplistically to me that, in business terms, DEC created or became
the brand leader for a net new market for minicomputers rather than
competing against the establish(ed, ing) market of large systems.  I'm
sure their marketers worked very hard to differentiate the systems
from large systems, precisely because they didn't want to compete with
anyone.  This is one of the most common motifs in technology business,
start with a small niche and build out.  It happened with UNIX, PCs,
networking, etc.  These things also usually follow power laws, where
only a couple companies control the market.  There are awesome plate
tectonics and associated earthquakes, disasters, and rebuilding from
ashes where markets collide, like UNIX systems taking on system of
record, transaction processing, CAD in the '80s-'90s against
mainframes, and the associated brand names tend to reshuffle (i.e. Sun
for a while).

Regards,

On Wed, Dec 27, 2017 at 3:25 PM, Dave Ritchie via TUHS
<tuhs at minnie.tuhs.org> wrote:
>
> I think that steep educational discounts and equipment grants from Digital
> to major collages also had a major impact,
> as did the existence of DECUS that made a lot of software readily available.
>
> Best regards,
> David Ritchie


  parent reply	other threads:[~2017-12-27 23:38 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <109152082.5216233.1514413535270.ref@mail.yahoo.com>
2017-12-27 22:25 ` Dave Ritchie
2017-12-27 22:32   ` Dave Horsfall
2017-12-27 23:44     ` Paul Winalski
2017-12-27 23:38   ` Kevin Bowling [this message]
2017-12-28  0:07     ` Paul Winalski
2017-12-28  0:45       ` Kevin Bowling
2017-12-28  1:39       ` Ron Natalie
2017-12-31  5:20 Rudi Blom
2017-12-31 12:56 ` Clement T. Cole
2017-12-31 15:03   ` Steve Simon
  -- strict thread matches above, loose matches on Subject: below --
2017-12-29 16:38 Larry McVoy
2017-12-29 23:54 ` Kevin Bowling
2017-12-30  0:04   ` Larry McVoy
2017-12-30  0:54   ` Lawrence Stewart
2017-12-30  1:47     ` Kevin Bowling
2017-12-30  2:19       ` Lawrence Stewart
2017-12-30  2:35         ` Paul Winalski
2017-12-30  2:20       ` Paul Winalski
2017-12-31  2:47     ` Henry Bent
2017-12-30  1:07   ` Ron Natalie
2017-12-30  2:30     ` Paul Winalski
2017-12-31  3:00       ` Henry Bent
2017-12-31  9:59         ` Arrigo Triulzi
2017-12-31 15:55         ` Paul Winalski
2017-12-28 14:05 Noel Chiappa
2017-12-28 15:59 ` Paul Winalski
2017-12-28 16:08   ` Larry McVoy
2017-12-28 23:28     ` Theodore Ts'o
2017-12-29 11:04       ` Kevin Bowling
2017-12-29 23:35         ` Jon Forrest
2017-12-29 23:58           ` Larry McVoy
2017-12-27 21:02 Alec Muffett
2017-12-27 21:50 ` Grant Taylor
2017-12-28  1:23   ` Alec Muffett
2017-12-27 21:51 ` Clem Cole
2017-12-27 21:52   ` Clem Cole
2017-12-28  2:14   ` Greg 'groggy' Lehey

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='CAK7dMtAoa8bPWrY9z=Ch6_QfH4nJnq-YQpX4WHXFiyVLnLD5gw@mail.gmail.com' \
    --to=kevin.bowling@kev009.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).