9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Tharaneedharan Vilwanathan" <dharani@lucent.com>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] GCC3.0 [Was; Webbrowser]
Date: Thu,  6 Feb 2003 16:29:31 -0500	[thread overview]
Message-ID: <017301c2ce26$d62b0d60$4ef0b487@bl.belllabs.com> (raw)
In-Reply-To: <20030206201354.8681.qmail@mail.dirac.net>

Hi,

> > I wouldnt worry about the 10% performance difference between Plan 9
> > implementation and FreeBSD or Linux. What matters is whether we can
> > tolerate the performance loss. As long as my apps like acme, sam,
charon,
> > etc run sufficiently fast, why would I worry?
>
> > > We know Plan 9 has the better design, code, capabilities, etc. It
would
> > > be nice at some point to be able to say that speed is a distinguishing
> > > feature of Plan 9. Is it fundamentally impossible?
>
> This is an important issue if we want Plan 9 to be more widely deployed.
I guess that not many users care about 10% differences in performance - but
if Plan 9 is (say) three times slower than Unix, its user base will always
be limited.

The strengths of Plan 9 should be the reason for wide deployment instead of
performance figures. Things like venti, fossil, factotum and revved up
graphics module are excellent additions to Plan 9 in the recent time. I
would like to see these kind of enhancements to Plan 9 rather than racing
with other OS'es in terms of performance. Of course, if someone can cleanly
modify the code for some critical performance improvement, thats fine.
Otherwise, let us not try to make Plan 9 another *nux* or *BSD.

IMHO.

Regards
dharani

PS: The opinions are just mine, not company's.





  reply	other threads:[~2003-02-06 21:29 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-06 20:13 Keith Nash
2003-02-06 21:29 ` Tharaneedharan Vilwanathan [this message]
2003-02-06 21:33   ` Russ Cox
2003-02-06 21:40     ` Jack Johnson
2003-02-07  8:44       ` Richard Miller
2003-02-07 13:51         ` matt
2003-02-07 14:03           ` Boyd Roberts
2003-02-07  0:06     ` Geoff Collyer
2003-02-07  5:32     ` Skip Tavakkolian
  -- strict thread matches above, loose matches on Subject: below --
2003-02-07  1:46 okamoto
2003-02-06 17:50 C H Forsyth
2003-02-06 18:08 ` Ronald G. Minnich
2003-02-06  5:28 okamoto
2003-02-06  5:40 ` andrey mirtchovski
2003-02-06 15:15 ` Ronald G. Minnich
2003-02-06 15:39   ` Tharaneedharan Vilwanathan
2003-02-06 15:45     ` Ronald G. Minnich
2003-02-06 16:31       ` rob pike, esq.
2003-02-06 16:36         ` rob pike, esq.
2003-02-06 16:56           ` matt
2003-02-06 17:11             ` Ronald G. Minnich
2003-02-06 17:25               ` Tharaneedharan Vilwanathan
2003-02-06 17:32                 ` andrey mirtchovski
2003-02-06 17:44               ` Sam
2003-02-06 18:07                 ` Ronald G. Minnich
2003-02-06 18:14                   ` David Presotto
2003-02-06 18:17                     ` Ronald G. Minnich
2003-02-06 20:36                       ` Dean Prichard
2003-02-06 18:35                     ` andrey mirtchovski
2003-02-06 18:43                       ` David Presotto
2003-02-06 19:12                         ` David Presotto
2003-02-06 19:20                       ` Scott Schwartz
2003-02-06 17:23       ` David Butler
2003-02-06  1:19 [9fans] Webbrowser Russ Cox
2003-02-06  3:00 ` [9fans] GCC3.0 [Was; Webbrowser] andrey mirtchovski
2003-02-06  4:16   ` andrey mirtchovski
2003-02-06 14:24     ` David Presotto
2003-02-06 15:30       ` andrey mirtchovski
2003-02-06 17:32         ` David Presotto
2003-02-06 18:10           ` William K. Josephson
2003-02-06 18:16             ` Ronald G. Minnich
2003-02-06 18:23               ` William K. Josephson
2003-02-06 21:09                 ` Ronald G. Minnich

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='017301c2ce26$d62b0d60$4ef0b487@bl.belllabs.com' \
    --to=dharani@lucent.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).