From: paul.winalski@gmail.com (Paul Winalski)
Subject: [TUHS] Why did PDPs become so popular?
Date: Wed, 27 Dec 2017 18:44:07 -0500 [thread overview]
Message-ID: <CABH=_VSCoMv9S5uK8YaN00u=cViNajKTcQ+TSSgR6XZS49VtwQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.BSF.2.21.1712280928320.64029@aneurin.horsfall.org>
On 12/27/17, Dave Horsfall <dave at horsfall.org> wrote:
> On Wed, 27 Dec 2017, Dave Ritchie via TUHS 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.
>
> IBM practically gave away their kit to educational institutions too (and
> made their money from the maintenance); there was no way that the
> University of NSW e.g. could've afforded their 360/50 otherwise,
That may have been true in the 1960s, but by the mid-1970s IBM
System/360/370 was no longer competitive in the educational market.
Circa 1973, Boston College--a true Blue IBM shop with a
System/370-145--wanted to provide time-sharing services to the student
body. For less than the cost to upgrade the model 145 to a 158, they
bought a PDP-11/70 and ran RSTS on it. Similarly Holy Cross (my alma
mater) had outgrown their System/370-125 by 1976. For the price of an
upgrade to a model 135, they could by a complete VAX-11/780 system for
academic use and retain the S/370-125 exclusively for college admin
purposes. The 11/780 was equivalent in compute power and memory
capacity to a S/370-158, but for about 1/4 the cost.
-Paul W.
next prev parent reply other threads:[~2017-12-27 23:44 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 [this message]
2017-12-27 23:38 ` Kevin Bowling
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='CABH=_VSCoMv9S5uK8YaN00u=cViNajKTcQ+TSSgR6XZS49VtwQ@mail.gmail.com' \
--to=paul.winalski@gmail.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).