Computer Old Farts Forum
 help / color / mirror / Atom feed
From: steve jenkin <sjenkin@canb.auug.org.au>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Cc: coff@tuhs.org
Subject: [COFF] Re: Terminology query - 'system process'?
Date: Sun, 31 Dec 2023 14:51:02 +1100	[thread overview]
Message-ID: <45D745E8-8CAA-4236-ACDA-CD785B519749@canb.auug.org.au> (raw)
In-Reply-To: <20231220193141.DC1C918C092@mercury.lcs.mit.edu>

Noel,

Adding a little to your observation on how fast CMOS microprocessors took over.

Wasn’t just DEC and IBM who were in financial trouble in 1992:
 - the whole US minicomputer industry had been hit.

DEC did well to just survive, albeit only for another 5 years before merging with HP.

steve j

> On 21 Dec 2023, at 06:31, Noel Chiappa <jnc@mercury.lcs.mit.edu> wrote:
> 
> I'm impressed, in retrospect, with how quickly the world went from proceesors
> built with transistors, through proceesors built out discrete ICs, to
> microprocessors. To give an example; the first DEC machine with an IC
> processor was the -11/20, in 1970 (the KI10 was 1972); starting with the
> LSI-11, in 1975, DEC started using microprocessors; the last PDP-11 with a
> CPU made out of of discrete ICs was the -11/44, in 1979. All -11's produced
> after that used microprocessors.
> 
> So just 10 years... Wow.
> 
> Noel

============

<http://archive.computerhistory.org/resources/access/text/2018/08/102740418-05-01-acc.pdf> [ 1,070 pg ]
<https://gordonbell.azurewebsites.net/Digital/Minicomputers_The_DEC_aka_Digital_Story.ppt> [ power point ]

The Birth and Passing of Minicomputers: From A Digital Equipment Corp. (DEC) Perspective
Gordon Bell
11 October 2006

(intro slide)

(DEC) 1957-1998. 41 yrs., 4 generations: transistor, IC, VLSI, clusters - winner take all
How computer classes form...and die.
Not dealing with technology = change = disruption

pg 21

91 Minicomputer companies 1984
by 1990 only 4 survived. (DG, DEC, HP, IBM)

============

--
Steve Jenkin, IT Systems and Design 
0412 786 915 (+61 412 786 915)
PO Box 38, Kippax ACT 2615, AUSTRALIA

mailto:sjenkin@canb.auug.org.au http://members.tip.net.au/~sjenkin


  parent reply	other threads:[~2023-12-31  3:51 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-20 19:31 Noel Chiappa
2023-12-20 20:29 ` Paul Winalski
2023-12-31  3:51 ` steve jenkin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-20 20:35 Noel Chiappa
2023-12-14 23:29 Noel Chiappa
2023-12-14 23:54 ` Larry McVoy
2023-12-15  1:15 ` Bakul Shah
2023-12-15 17:51   ` Paul Winalski
2023-12-15 18:08     ` Warner Losh
2023-12-16  2:04     ` Greg 'groggy' Lehey
2023-12-16 19:21       ` Paul Winalski
2023-12-16 19:44         ` Paul Winalski
2023-12-15 13:43 ` Dan Cross
2023-12-19 13:54 ` Derek Fawcus via COFF
2023-12-14 21:48 [COFF] " Noel Chiappa
2023-12-14 22:06 ` [COFF] " Bakul Shah
2023-12-14 22:12   ` Warner Losh
2023-12-14 22:09 ` Clem Cole
2023-12-15 14:20   ` Dan Cross
2023-12-15 16:25     ` Warner Losh
2023-12-15 17:13     ` Bakul Shah
2023-12-15  6:24 ` Lars Brinkhoff
2023-12-15 18:30   ` Stuff Received

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=45D745E8-8CAA-4236-ACDA-CD785B519749@canb.auug.org.au \
    --to=sjenkin@canb.auug.org.au \
    --cc=coff@tuhs.org \
    --cc=jnc@mercury.lcs.mit.edu \
    /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).