9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Christopher Browne <cbbrowne@news.isp.giganews.com>
To: 9fans@cse.psu.edu
Subject: [9fans] Re: Kernighan interview (w/ Plan 9 mention)
Date: Wed,  6 Sep 2000 08:45:04 +0000	[thread overview]
Message-ID: <M_gt5.62762$g53.1009553@news5.giganews.com> (raw)
In-Reply-To: <bqwu2buc44y.fsf@bronze.lcs.mit.edu>

Centuries ago, Nostradamus foresaw a time when Conway Yee would say:
>Leo Caves <caves@ysbl.york.ac.uk> writes:
>> Arguably, Linux transitioned from its hobbyist niche
>> to a wider acceptance through a server role.  The effort now
>> seems to be back to the desktop.
>> 
>> Its difficult to tell in what way Plan 9 might make such a transition.
>
>I would argue that such a transition will likely never take place.
>
>First, there is usually only room for 1 "killer app" in the market and
>Linux has already taken up that role.

_Partially_ true...

The "killer app" that I'd consider Linux provides is a "freely
licensed, freely modifiable environment in which to run All Sorts Of
Unix Code."

That's not "so killer" as to have prevented there from being quite
viable teams working on FreeBSD, NetBSD, and OpenBSD, that provide
much the same "killer app."

The problem for Plan 9 is that it _isn't_ quite such a platform.  It's
_not_ "more-or-less a Unix clone."

While there are common roots with Unix, the way Plan 9 proves really
useful is if it is used to do things you couldn't do with Unix.

There is a close parallel here with Hurd; the major _merit_ of Hurd,
over Linux, is the ability to do Cool Stuff using the Hurd translators
that provide cool mappings of system facilities onto filesystems.  

The problem with this is that if you write applications that depend on
"Cool Stuff" like Hurd translators or Plan 9 namespaces, those
applications can't run anywhere else.  Which makes them "niche" apps,
which will be largely ignored by the large proportion of the
population that use more "mainstream" systems.

You may have a cool HTTP server where all the behaviour/configuration
is exposed as a virtual filesystem; if it only runs on Plan 9,
interest will be limited to the point of extinction.

>Second, who can forget the litigation over NET/2?  Anyone who
>contributes with the intent of transitioning to a server role will
>eventually have to deal with ATT's lawyers.  I believe that the
>engineers/scientists at ATT are honorable but are their lawyers?
>
>Third, as it stands, Plan 9's license is hardly appropriate to those
>who would run it for serious applications.  Who wants to take the risk
>of having ATT own your application?

This just makes things worse; even if the lawyers _are_ honorable,
nobody knows for sure until _after_ they deploy the applications, and
the uncertainty will be crippling.
-- 
(concatenate 'string "aa454" "@" "freenet.carleton.ca")
<http://www.hex.net/~cbbrowne/>
Rules of the Evil Overlord #83. "If I'm eating dinner with the hero,
put poison in his goblet, then have to leave the table for any reason,
I will order new drinks for both of us instead of trying to decide
whether or not to switch with him." <http://www.eviloverlord.com/>



  parent reply	other threads:[~2000-09-06  8:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-05 13:29 [9fans] " Leo Caves
2000-09-05 14:27 ` [9fans] " Conway Yee
2000-09-05 16:59   ` Douglas A. Gwyn
2000-09-06  8:45     ` George Michaelson
2000-09-06 13:32       ` Boyd Roberts
2000-09-06 13:21     ` Boyd Roberts
2000-09-06 19:45       ` Boyd Roberts
2000-09-06  8:45   ` Christopher Browne [this message]
2000-09-06 10:35   ` Michael Jeffrey.
2000-09-06 13:43   ` Boyd Roberts
2000-09-06 13:09 bwc
2000-09-06 13:24 rob pike
2000-09-06 13:24 forsyth
2000-09-06 22:21 ` Boyd Roberts
2000-09-06 22:31 ` Boyd Roberts

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='M_gt5.62762$g53.1009553@news5.giganews.com' \
    --to=cbbrowne@news.isp.giganews.com \
    --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).