Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/5/84; site terak.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!think!harvard!seismo!hao!noao!terak!doug
From: doug@terak.UUCP (Doug Pardee)
Newsgroups: net.lang.c
Subject: Re: Dying Architectures
Message-ID: <803@terak.UUCP>
Date: Thu, 17-Oct-85 13:32:47 EDT
Article-I.D.: terak.803
Posted: Thu Oct 17 13:32:47 1985
Date-Received: Sun, 20-Oct-85 06:23:42 EDT
References: <1964@brl-tgr.ARPA> <205@mips.UUCP> <131@nbires.UUCP>
Organization: Calcomp Display Products Division, Scottsdale, AZ, USA
Lines: 22

[why is this here instead of net.arch?]

> the whole IBM mainframe
> line is architecturally right where it started--in the mid-'60's.  That
> they have such a huge installed base in spite of a crippled architecture
> (like a 4K forward-only offset in instructions) is a tribute to IBM's
> marketing, sales, and support organizations--certainly not to the
> architecture of their machines.

Not to take anything away from IBM's very strong marketing, sales, and
support organizations, but...

Something else that IBM understands is that the CUSTOMER is the most
important person there is, and that the customer wants results; the
customer doesn't give a hang about computer architecture and systems
programming languages.  The customer wants a machine that'll run his
telecommunications network and his database.  The customer wants a
machine that will run his programming staff's COBOL programs.  He 
doesn't give a *hoot* if the operating system is written in assembler,
PL/S, or C, or how many registers and addressing modes the CPU supports.
-- 
Doug Pardee -- CalComp -- {calcom1,savax,seismo,decvax,ihnp4}!terak!doug