The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: scj@yaccman.com (Steve Johnson)
Subject: [TUHS] long lived programs (was Re: RIP John Backus
Date: Mon, 26 Mar 2018 18:21:49 -0700	[thread overview]
Message-ID: <cc3c05aa2a06dcc9c0a61c18649d9f03a4880097@webmail.yaccman.com> (raw)
In-Reply-To: <D51BFDAA-889B-4A9F-BAA4-8A961FFB7F8D@tfeb.org>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2521 bytes --]

Portability and standard API are very good for users, but
manufacturers hate them.  Unix portability was supported by AT&T in
part because they were getting flak from non-DEC manufacturers about
Unix running only on the PDP-11.   Once Unix was ported,
applications could run on hardware that was cheapest and most
appropriate to the application rather than where it was first
written.  Users, much more than computer companies, benefited from
portability.  And DARPA, with a similarly broad view, for the most
part did things that helped users rather than specific manufacturers.

In fact, the first thing most manufacturers did with Unix was to
change it.  The rot set in quickly, leading to long boring chaotic
standards efforts over POSIX and C (remember OSF?).

On the other hand, manufacturers love open source.   There are no
apparent limits on growth, and few guiding hands to prevent silly, or
downright dangerous features from creeping into the endlessly bloating
code bases.  Each company can get their own version at low cost and
keep their customers happy, serene in the knowledge that if the
customers try to use another system they will have to deal with the
100+ pages of incompatible GCC options and have to tame piles of
poorly concieved and documented code.  None of the stakeholders in
open source have anything to gain by being compatible, or even letting
people know when they change something incompatibly without warning. 
After all, it can only hurt the other stakeholders, not them...

Yes, I'm old and cynical, and yes there are some islands of sanity
fighting the general trend.   And yes, I think this is a cyclical
problem that will swing back towards sanity, hopefully soon.  But
where is the AT&T or DARPA with enough smarts and resources to do
things simply, and motivation to make users happy rather than
increasing profits?

Steve

----- Original Message -----
From: "Tim Bradshaw" <tfb@tfeb.org>. . .

To bring this back to Unix history, I think this is an example of a
place where Unix has failed (or, perhaps, where people have failed to
make use of it properly).  Half the reason these things are such a
trouble is that they aren't written to any really portable API, so the
bit that runs on Solaris isn't going to run on AIX or Linux, and it
only might run on the current version of Solaris in fact.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20180326/596b740f/attachment.html>


  parent reply	other threads:[~2018-03-27  1:21 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.21.1521314548.3788.tuhs@minnie.tuhs.org>
2018-03-17 20:14 ` [TUHS] " Paul McJones
2018-03-17 22:27   ` Steve Johnson
2018-03-22 21:05     ` [TUHS] long lived programs (was " Bakul Shah
2018-03-22 21:35       ` Clem Cole
2018-03-23 19:28         ` Bakul Shah
2018-03-23 19:44           ` Larry McVoy
2018-03-23 21:23           ` Clem Cole
2018-03-23 21:36             ` Warner Losh
2018-03-23 22:02               ` Steve Johnson
2018-03-26 13:43           ` Tim Bradshaw
2018-03-26 16:19             ` Paul Winalski
2018-03-26 16:41               ` Arthur Krewat
2018-03-26 19:53                 ` Larry McVoy
2018-03-27  1:08               ` Clem Cole
2018-03-26 19:04             ` Bakul Shah
2018-03-27  1:21             ` Steve Johnson [this message]
2018-03-27  1:46               ` Clem Cole
2018-03-23 10:43       ` Tim Bradshaw
     [not found]         ` <CAC20D2P1CZwaD0uJpMhWg11muDeH9rEn3X+AUjXvwMKsNjs7ng@mail.gmail.com>
2018-03-26  0:53           ` [TUHS] Fwd: " Clem Cole
2018-03-23  2:53 [TUHS] " Doug McIlroy
2018-03-23 18:27 ` Bakul Shah

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=cc3c05aa2a06dcc9c0a61c18649d9f03a4880097@webmail.yaccman.com \
    --to=scj@yaccman.com \
    /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).