9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: nigel@9fs.org
To: 9fans@cse.psu.edu
Subject: Re: [9fans] capability-based design (Re: permissions idea)
Date: Fri,  5 Oct 2001 09:13:57 +0100	[thread overview]
Message-ID: <20011005081358.C0554199B5@mail.cse.psu.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 348 bytes --]

>> the success rate compared with
>> proprietary OSes is rather good.  note that almost all proprietary
>> OSes have educated and experienced designers and implementors.
>>
I've a feeling that for every GPL'ed OS you can name which is successful,
I can name several non-GPL'ed ones. In fact, I can only think of one
successful GPLed OS...


[-- Attachment #2: Type: message/rfc822, Size: 2731 bytes --]

From: Richard <greon@best.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] capability-based design (Re: permissions idea)
Date: Fri, 05 Oct 2001 00:40:45 -0700
Message-ID: <E15pPbB-0002yN-00@localhost>

nigel@9fs.org writes:

>>> also, EROS's GPLed.  I do not say that is an improvement, but 
>>> a GPLed OS has done very well lately in popularity.
>
>This is a bit self-fulfilling isn't it? How many GPL'ed OSes are there
>thay haven't become popular? We don't know, because they haven't
>become popular enough to get publicised.

there are many GPLed OSes, but most are written by teenagers or young
men with little education or experience.  among GPLed OSes with
competent designers and implementors, the success rate compared with
proprietary OSes is rather good.  note that almost all proprietary
OSes have educated and experienced designers and implementors.

I am thinking also about the abandonment of AmigaOS, OS/2 and (probably)
BeOS.  it must be frustrating to have written software for one of those
once-popular platforms only to see the owner of the platform let it die.
I speculate that proprietary OSes need to attract 10s of millions of
users or their owners let them die, but that open source OSes can
survive for decades with much fewer users.

the "fitness landscape" for OSes is quite harsh and severe because
of numerous "network effects".  "network effect" is a term from
economics that every computerist should understand.

             reply	other threads:[~2001-10-05  8:13 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-05  8:13 nigel [this message]
2001-10-05 16:44 ` Richard
  -- strict thread matches above, loose matches on Subject: below --
2001-10-09  2:06 okamoto
2001-10-08 18:16 Sape Mullender
2001-10-08 18:18 ` Lucio De Re
2001-10-05 17:12 Russ Cox
2001-10-05  5:31 nigel
2001-10-05  7:40 ` Richard
2001-10-08  9:36   ` Thomas Bushnell, BSG
2001-10-05  4:00 okamoto
2001-10-08 16:53 ` Maarit Maliniemi 
2001-10-04 23:57 Richard
2001-10-04 21:59 forsyth
2001-10-04 23:29 ` Richard
2001-10-04 19:28 rog
2001-10-04 20:27 ` Richard
2001-10-04 20:33 ` Richard
2001-09-28  1:06 [9fans] on the topic of viruses dmr
2001-10-01 16:13 ` permissions idea (Re: [9fans] on the topic of viruses) Matthew Hannigan
2001-10-02  8:34   ` Douglas A. Gwyn
2001-10-04 18:36     ` [9fans] capability-based design (Re: permissions idea) Richard

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=20011005081358.C0554199B5@mail.cse.psu.edu \
    --to=nigel@9fs.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).