From: Paul Winalski <paul.winalski@gmail.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: Demise of AT&T
Date: Mon, 19 May 2025 12:18:15 -0400 [thread overview]
Message-ID: <CABH=_VSNMFbB=b31vynUcvtrrnSV=O3iNfHGjWRdv_H9j0Ba-w@mail.gmail.com> (raw)
In-Reply-To: <20250519134245.3F5CC18C088@mercury.lcs.mit.edu>
[-- Attachment #1: Type: text/plain, Size: 1445 bytes --]
On Mon, May 19, 2025 at 9:43 AM Noel Chiappa <jnc@mercury.lcs.mit.edu>
wrote:
> > It wasn't just AT&T, IBM & DEC that got run over by commodity DRAM &
> > CPU's, it was the entire Minicomputer Industry, effectively extinct
> by
> > 1995.
>
> Same thing for the work-station industry (with Sun being merely the most
> notable example).
>
Indeed. Extinction of existing practice by new technology happens all the
time and not just in the computer field. Before sound recording and
playback was invented, fancy restaurants, hotels, etc. hired orchestras to
play background music. The phonograph put a huge number of orchestras out
of business.
There's a knee-jerk tendency in our industry for companies to respond to
new technology by retreating to the high end of the market in an attempt to
protect profit margins. IBM did this when minicomputers came along; Apollo
did it when confronted with cheap workstations (Sun); DEC did it when the
PC appeared; Intel right now is attempting to do it to stave off
competition from ARM. In all cases the effort has been unsuccessful and
usually has resulted in the death of the company (IBM has survived, but as
a shadow of its former self).
I think it was Scott McNealy who said (regarding protecting existing
products and profit margins) that a tech company must be prepared to eat
its own children. If they don't, the competition will.
-Paul W.
[-- Attachment #2: Type: text/html, Size: 1856 bytes --]
next prev parent reply other threads:[~2025-05-19 16:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-19 13:42 Noel Chiappa
2025-05-19 16:18 ` Paul Winalski [this message]
2025-05-19 19:17 ` ron minnich
2025-05-19 19:44 ` [TUHS] Whither Workstations? (Was Re: Demise of AT&T) Dan Cross
2025-05-19 20:28 ` [TUHS] " segaloco via TUHS
2025-05-19 20:54 ` Dan Cross
2025-05-21 15:30 ` Stuart Remphrey
[not found] ` <2e11a860-253c-696f-e1d0-8907b40870e8@riddermarkfarm.ca>
[not found] ` <69CD1C29-0215-46EF-ADC3-527330F45208@canb.auug.org.au>
2025-05-27 23:03 ` Martin Schröder
[not found] ` <bb7cd052-7d3f-68e3-754f-59c84e341d10@makerlisp.com>
[not found] ` <1c8121e4-5011-8a63-1147-aa967e9ac872@makerlisp.com>
[not found] ` <7c4d912d-7512-ef74-7535-8239fb55bb27@makerlisp.com>
[not found] ` <d718e268-15d8-393b-6a4d-fb066f06d662@makerlisp.com>
[not found] ` <4318e32f-a1b1-c366-c36d-f210d047b379@makerlisp.com>
2025-05-28 7:18 ` Warren Toomey via TUHS
2025-05-23 20:25 ` Kevin Bowling
[not found] ` <gx0lVGH90f4F9Os4Ovj-VJy4NOciyBu7hmLl7kSJWh-3bGOX5-NWpZLoOcADoH7OXHp53rUJQvPmvyzydVjyqzf61VJgTpynSuY8Msgo-y8=@protonmail.com>
2025-05-26 23:26 ` [TUHS] Re: WE321 3B/VME boar (Re: Whither Workstations? (Was Re: Demise of AT&T)) Greg A. Woods
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=_VSNMFbB=b31vynUcvtrrnSV=O3iNfHGjWRdv_H9j0Ba-w@mail.gmail.com' \
--to=paul.winalski@gmail.com \
--cc=jnc@mercury.lcs.mit.edu \
--cc=tuhs@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).