9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Skip Tavakkolian <9nut@9netics.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Re: 9fans Digest, Vol 27, Issue 52
Date: Tue, 25 Jul 2006 11:20:30 -0700	[thread overview]
Message-ID: <8f2c08bbdbed717dd39e589bc9447e02@9netics.com> (raw)
In-Reply-To: <20060725060656.C57B6297F0@mail.bitblocks.com>

> Or may be its way is most suited for some future where
> computers as public transport for a variety of unrelated
> programs are a thing of the past?

yes; but future is now.  how many digital gizmos does a person have?
mobile phone, ipod, digital camera, pots phone. throw in a pda,
a laptop and a desktop and there it is.

what's the killer app for plan9?  the vector is toward distributed
access to resources.  9grid is extending the sharing to process space.
we're betting on our shared name space system.  apps for collaboration
are another area of possibility; checkout VN's solutions based on
inferno.  plan9 doesn't need to be "in your face" to be useful.  the
way we're using plan9, it is transparent to the end user.

the amount of success is directly related to the amount of money
behind the os or platform. linux offered real savings on
acquisition and maintenance over windows; windows' success was in
providing a common platform for "productivity" applications, that had
positive returns on investment to the user and revenue to the app
developer - the largest being ms itself.

once a killer app is created that shows a clear advantage for using
plan9 over other os, it will be adopted.  availability of p9p means
that app developers can take advantage of the model, while still
satisfying any dictated requirements for a more known os; this is
likely to be the case early in the adoption curve, despite the fact
that plan9 is much easier to learn and maintain than other os



      parent reply	other threads:[~2006-07-25 18:20 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20060724160009.A640A5AF70@mail.cse.psu.edu>
2006-07-24 16:38 ` Andrew Hudson
2006-07-24 19:28   ` Ronald G Minnich
2006-07-24 19:49     ` csant
2006-07-24 19:53       ` John Floren
2006-07-24 20:19         ` [9fans] missing applications Lyndon Nerenberg
2006-07-24 20:22           ` John Floren
2006-07-25 10:29             ` Harri Haataja
2006-07-25 15:06               ` David Leimbach
2006-07-25 19:53               ` Robert Raschke
2006-07-25 21:25               ` Sascha Retzki
2006-07-25 17:52                 ` David Leimbach
2006-07-25 18:32                   ` Harri Haataja
2006-07-25 18:26                 ` Harri Haataja
2006-07-25 18:33                   ` andrey mirtchovski
2006-07-25 18:47                     ` Harri Haataja
2006-07-24 22:41         ` [9fans] Re: 9fans Digest, Vol 27, Issue 52 Micah Stetson
2006-07-24 23:17           ` Jack Johnson
2006-07-24 20:02       ` Ronald G Minnich
2006-07-24 20:02       ` Ronald G Minnich
2006-07-24 20:08         ` csant
2006-07-24 20:23           ` David Leimbach
2006-07-24 20:31           ` Ronald G Minnich
2006-07-24 20:43             ` David Leimbach
2006-07-24 20:21       ` David Leimbach
2006-07-24 20:26         ` John Floren
2006-07-25  0:17         ` Sascha Retzki
2006-07-24 20:36           ` andrey mirtchovski
2006-07-24 20:51             ` David Leimbach
2006-07-24 20:42           ` David Leimbach
2006-07-24 21:15           ` Skip Tavakkolian
2006-07-24 23:28             ` David Leimbach
2006-07-25 13:38               ` rog
2006-07-25 14:58                 ` Darren Bane
2006-07-24 23:59       ` Sascha Retzki
2006-07-24 20:26         ` Richard Miller
2006-07-24 23:48         ` erik quanstrom
2006-07-25  2:50       ` Dan Cross
2006-07-25  3:01         ` John Floren
2006-07-25  3:58         ` Federico G. Benavento
2006-07-25  5:35           ` David Leimbach
2006-07-25  6:06         ` Bakul Shah
2006-07-25 10:34           ` John Pritchard
2006-07-25 20:17             ` erik quanstrom
2006-07-25 21:23               ` Francisco J Ballesteros
2006-07-25 21:27                 ` Paul Hebble
2006-07-25 21:41                   ` Francisco J Ballesteros
2006-07-25 22:28                 ` David Leimbach
2006-07-25 22:38                   ` Francisco J Ballesteros
2006-07-25 23:32                 ` erik quanstrom
2006-07-25 22:59               ` csant
2006-07-25 23:28                 ` erik quanstrom
2006-07-26 17:40                   ` Sascha Retzki
2006-07-26 17:55                     ` Lou Kamenov
2006-07-26 17:57                       ` Sascha Retzki
2006-07-26 17:58                       ` Lou Kamenov
2006-07-26 18:13                         ` Skip Tavakkolian
2006-07-26 18:15                           ` Lou Kamenov
2006-07-26 20:40                         ` [9fans] small devices Charles Forsyth
2006-07-26 21:03                           ` lucio
2006-07-26 21:18                           ` Paul Lalonde
2006-07-26 21:35                             ` csant
2006-07-26 21:37                           ` Ronald G Minnich
2006-07-27  0:41                             ` LiteStar numnums
2006-07-25 18:20           ` Skip Tavakkolian [this message]

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=8f2c08bbdbed717dd39e589bc9447e02@9netics.com \
    --to=9nut@9netics.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).