9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Richard Uhtenwoldt <ru@river.org>
To: 9fans@cse.psu.edu
Subject: [9fans] software quality and popularity
Date: Tue, 22 May 2001 12:28:14 -0700	[thread overview]
Message-ID: <200105221928.MAA02159@ohio.river.org> (raw)
In-Reply-To: <20010426234625.1EBA119A40@mail.cse.psu.edu>

geoff.9fans@collyer.net writes:

>Popularity and quality are not related.  (A more pessimistic view is
>that they are related, but inversely.  The current state of operating
>systems, languages and software generally tends to support that view.)

William K. Josephson writes:

>In fact, in my experience, the Plan 9
>source code is far *more* portable to other environments than most
>Unix source is between Unix variants, for instance.

well, you see, if all code written for Plan 9 can be easily ported to
Unix, but the code written for Unix is difficult to port to Plan 9
(because Unix is not as well thought out and well factored as Plan 9),
then people who want to use apps without having to port/rewrite/write
them will choose  Unix, because the apps available for Unix will
tend to be a superset of the apps available for Plan 9.

so here we have a process whereby bad engineering actually 
increases a platform's popularity.  (Dijkstra noted a similar process
back in the 1970s in which DP department workers increased their job
security by choosing overly complex solutions, which IBM was happy to
sell to them.)

and even people like me, who appreciate well-engineered, well-factored
software, choose to use one of the popular, poorly-engineered
platforms, because the socioeconomic utility of a platform is
essentially proportional to the number of users of the platform.
(reasons for this omitted for space reasons.)  so, I put up with the
cost in my wasted time of the poor engineering to get the
socioeconomic benefits of the popularity.

eventually a critical mass of (millions of) users will come to
recognize the true costs of poorly-engineered software, resulting in
popular software as well-engineered as Plan 9, but that is not going
to happen this decade.

what is going happen this decade to help along the eventual popularity
of well-engineered software more than anything else is the replacement
of data formats, communications protocols, APIs with secrets and
"owners" (firms with the ability to prevent their competitors from
making full use of the data format, etc) with data formats, protocols
and APIs without secrets and owners.

so, even tho the open-source platforms like Linux are poorly
engineered, the more popular they get, the better for unpopular
platforms, and thus well-engineered platforms in the long term,
because Linux's data formats, protocols and APIs have no secrets and
no "owners" so that the unpopular platforms can hook into them more
effectively.  one example of this hooking in is the consulting of
Linux device-driver source code by Plan 9 developers.

this hooking in gives the users of the unpopular platform a bigger
fraction of the socioeconomic benefits of Linux than they could get
from the unpopular platform's trying to hook into proprietary
platforms, because the "owners" of the proprietary platforms will tend
to prevent competition from other platforms by denying those benefits.



  reply	other threads:[~2001-05-22 19:28 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-26 23:46 [9fans] Awk or Limbo ? geoff.9fans
2001-05-22 19:28 ` Richard Uhtenwoldt [this message]
2001-05-22 20:10   ` [9fans] software quality and popularity Boyd Roberts
2001-05-22 22:12     ` andrey mirtchovski
2001-05-22 22:34     ` William Staniewicz
2001-05-23  8:24       ` Douglas A. Gwyn
2001-05-22 20:31 Russ Cox
2001-05-22 21:28 ` Dan Cross
2001-05-22 22:39 Eric Grosse
2001-05-22 23:26 jmk
2001-05-23 14:57 ` Douglas A. Gwyn
2001-05-23  0:58 okamoto
2001-05-23  1:01 rob pike
2001-05-23  1:15 ` Boyd Roberts
2001-05-23 14:56   ` Douglas A. Gwyn
2001-05-23  1:27 okamoto
2001-05-23  6:47 ` Boyd Roberts
2001-05-23 15:38 Russ Cox
2001-05-23 15:39 jmk
2001-05-24  8:46 ` Douglas A. Gwyn
2001-05-24 14:34   ` David Lukes
2001-05-23 18:45 David Gordon Hogan
2001-05-24  8:46 ` Douglas A. Gwyn
2001-05-24 12:01 jmk
2001-05-24 14:14 ` Douglas A. Gwyn
2001-05-24 15:31 ` David Lukes
2001-05-24 14:42 jmk
2001-05-24 16:08 ` Dan Cross
2001-05-25  0:48 okamoto
2001-05-25  8:21 ` Douglas A. Gwyn
2001-05-25  2:09 okamoto

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=200105221928.MAA02159@ohio.river.org \
    --to=ru@river.org \
    --cc=9fans@cse.psu.edu \
    /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).