Computer Old Farts Forum
 help / color / mirror / Atom feed
From: steve jenkin <sjenkin@canb.auug.org.au>
To: COFF <coff@tuhs.org>
Subject: [COFF] Butler Lampson's 1973 Xerox PARC memo "Why Alto?"
Date: Sat, 8 Jul 2023 17:45:36 +1000	[thread overview]
Message-ID: <5E4113AB-AAF8-42D1-9A75-DF6BF659251A@canb.auug.org.au> (raw)

What struck me reading this is the estimated price (~$10K) to build an Alto, elsewhere I’ve seen $12K and 80 built in the first run.
 [ a note elsewhere says $4,000 on 128KB of RAM. 4k-bit or 16-kbit chips? unsure ]

I believe the first "PDP-11” bought by 127 at Bell Labs was ~$65k fully configured (Doug M could confirm or not), although the disk drive took some time to come.
Later, that model was called PDP-11/20.

Why the price difference?

PARC was doing DIY - it’s parts only, not a commercial production run with wages, space, tooling & R+D costs and marketing/sales to be amortised,
with a 80%+ Gross Margin  required, as per DEC.

Why didn’t Bell Labs build their own “Personal Computer” like PARC?
They had the need, the vision, the knowledge & expertise.

I’d suggest three reasons:

	- The Consent Decree. AT&T couldn’t get into the Computer Market, only able to build computers for internal use.
		They didn’t need GUI PC’s to run telephone exchanges.

	- Bell Labs management:
		they’d been burned by MULTICS and, rightly, refused the CSRC a PDP-10 in 1969.

	- Nobody ’needed’ to save money building another DIY low-performance device.
		A home-grown supercomputer maybe :)


It’s an accident of history that PARC could’ve, but didn’t, port Unix to the Alto in 1974.
By V7 in 1978, my guess it was too late because both sides had locked in ‘commercial’ positions and for PARC to rewrite code wasn’t justified: “If it ain’t Broke”… 

Porting Unix before 1974 was possible:
	PARC are sure to have had close contact with UC Berkeley and the hardware/software groups there.

Then 10 years later both Apple and Microsoft re-invent Graphical computing using commodity VLSI cpu’s.

Which was exactly the technology innovation path planned by Alan Kay in 1970:

	build today what’ll be cheap hardware in 10 years and figure out how to use it.

Ironic that in 1994 there was the big Apple v Microsoft  lawsuit over GUI’s & who owned what I.P.
Xerox woke up up midway through and filed their own infringement suit, and lost.
 [ dismissed because approx they'd waited too long ]

	<https://en.wikipedia.org/wiki/Apple_Computer,_Inc._v._Microsoft_Corp.>

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

PDF:
	<http://bwl-website.s3-website.us-east-2.amazonaws.com/38a-WhyAlto/Acrobat.pdf>

Other formats:
	<http://bwl-website.s3-website.us-east-2.amazonaws.com/38a-WhyAlto/Abstract.html>

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

--
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


             reply	other threads:[~2023-07-08  7:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-08  7:45 steve jenkin [this message]
2023-07-09 21:03 ` [COFF] " Clem Cole
2023-07-09 21:51   ` Larry Stewart

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=5E4113AB-AAF8-42D1-9A75-DF6BF659251A@canb.auug.org.au \
    --to=sjenkin@canb.auug.org.au \
    --cc=coff@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).