From: Paul Eggert <eggert@cs.ucla.edu>
To: Frank da Cruz <fdc@columbia.edu>,
"Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Liam Stitt <stittl@cuug.ab.ca>, Mike <michael@rmrco.com>,
GNU C Library <libc-alpha@sourceware.org>
Subject: Re: C-kermit fails
Date: Fri, 31 Jul 2020 13:23:27 -0700 [thread overview]
Message-ID: <e600a7a3-7bed-f11a-7963-dff59948003c@cs.ucla.edu> (raw)
In-Reply-To: <CAKqtx9-eJ5P+SLWz7zm-VQm9YNy+Y_uRfDWw0iysz=as2uTRNw@mail.gmail.com>
On 7/31/20 11:22 AM, Frank da Cruz wrote:
> Software development was not like
> this when computing was dominated by companies like IBM and DEC, who were
> dedicated to preserving their customers' investments in software because if
> they didn't, they'd lose those customers.
That wasn't my experience at all. IBM and DEC regularly broke user applications
and said the equivalent of "If you don't like it, then just keep running the old
OS on the old hardware." They then tried to sell you new stuff, and if you
refused they eventually stopped supporting the old stuff.
For example, circa 1978 if you wanted to use a PDP-11/70 and selected DEC's
operating system RSTS, you would have been kinda out of luck by around 1983 when
the PDP-11/70 was obsolete. DEC told customers to switch to VAX/VMS, and gave
some upgrade paths (late-1970s VAX hardware would emulate PDP-11s and if you
threw DEC some more money VMS would support RSTS user processes, albeit
inefficiently) but DEC dropped those upgrade paths in later VAX hardware and you
were stuck. The last RSTS release was in 1992 and DEC stopped supporting RSTS
soon after.
Had you selected Unix instead in 1978, you'd have been golden. Your software
would still run today, with only minor changes. I still run some personal
Unix-based software now that I originally ran on a PDP-11 in the late 1970s.
And it wasn't just DEC. I remember the FAA using IBM mainframes in their air
traffic control systems designed in the 1960s and written in 360 assembler with
CCW programs. The FAA kept running this stuff on an old IBM OS on old IBM
hardware until IBM told them around 1980 that IBM wouldn't support it any more.
IBM then sold the FAA on a replacement system called AAS that cost billions and
never worked. See
<https://www.sebokwiki.org/wiki/Federal_Aviation_Administration_(FAA)_Advanced_Automation_System_(AAS)>
for some of this sad history.
Although I'm sure one can cite examples of old-time backward compatibility, I'm
exceedingly skeptical that the old days were any better than now overall in that
department. Quite the contrary. In particular, the GNU C library is *much*
better about backward compatibility than IBM and DEC were in the "good old days".
next prev parent reply other threads:[~2020-07-31 20:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-24 16:29 C-kermit fails Mike
2020-07-24 16:33 ` Florian Weimer
2020-07-24 17:36 ` Zack Weinberg
2020-07-24 18:47 ` Paul Eggert
2020-07-24 19:41 ` Frank da Cruz
2020-07-24 19:45 ` Frank da Cruz
2020-07-24 20:05 ` Zack Weinberg
2020-07-27 8:10 ` Florian Weimer via Libc-alpha
2020-07-24 21:07 ` Paul Eggert
2020-07-24 23:45 ` Frank da Cruz
2020-07-25 1:59 ` Paul Eggert
2020-07-31 12:41 ` Maciej W. Rozycki
2020-07-31 18:22 ` Frank da Cruz
2020-07-31 20:23 ` Paul Eggert [this message]
2020-08-01 0:17 ` Frank da Cruz
2020-08-01 8:07 ` Paul Eggert
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e600a7a3-7bed-f11a-7963-dff59948003c@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=fdc@columbia.edu \
--cc=libc-alpha@sourceware.org \
--cc=macro@linux-mips.org \
--cc=michael@rmrco.com \
--cc=stittl@cuug.ab.ca \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).