9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@speakeasy.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] design issues in operating systems
Date: Tue,  4 Dec 2001 12:27:44 -0500	[thread overview]
Message-ID: <20011204172744.411EF3F414@quanstro.net> (raw)


> On Mon Dec  3 15:52:18 EST 2001, mike@ducky.net wrote:
> > I suspect one important factor in the popularity of Linux
> > is the relative openness of the development process of Linux.
> > There are regular releases of the latest version of the
> > code, even when there are works in progress that aren't
> > finished yet.
> >
> > By contrast the Plan 9 developers are constantly dropping
> > all these hints about how great the next thing will be,
> > but the rest of us never get to see any code until it's
> > "done" -- and big changes take a long time.
> >
> > I think Plan 9 would have a more enthusiastic following
> > if the ongoing development tree were out there for everyone
> > to see (and contribute to).
>
> Do we hint that the next thing will be great? If so, we should stop.
> It may or may not be great but it will be different, I think that's
> about as far as I'd be willing to go.

in so many words, i think so.

9p2000 has been talked about on this list for quite some time now.
(i'm waiting with baited breath to see it.) and rather than somebody
/saying/ that the next thing will be great, i think that folks have
gotten excited to see the 9p2000 without any hype. i know i have.

don't stop dropping tidbits. they're interesting. but i think mike's
point is that having something akin to (for lack of a better analogy)
the linux development series (e.g. x.y.z where y is odd) would be a
Good Thing.

of course, doing this isn't free. it takes time & effort to release.
and releasing early & often take time early & often.


             reply	other threads:[~2001-12-04 17:27 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-04 17:27 erik quanstrom [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-12-05  8:49 Fco.J.Ballesteros
2001-12-04 10:36 forsyth
2001-12-03 22:50 jmk
2001-12-03 21:34 rob pike
2001-12-03 22:01 ` Alexander Viro
2001-12-04 19:05   ` Dan Cross
2001-12-04 21:59     ` Alexander Viro
2001-12-07  9:36       ` Barry
2001-12-03 21:31 rob pike
2001-12-03 16:27 presotto
2001-12-03 16:07 anothy
2001-12-03 16:04 ` Lucio De Re
2001-12-03 15:45 bwc
2001-12-03 14:49 bwc
2001-12-02 17:05 Andrey A Mirtchovski
2001-12-03 10:09 ` josh d
2001-12-03 15:24   ` Ronald G Minnich
2001-12-03 15:08     ` Lucio De Re
2001-12-03 15:48     ` andrey
2001-12-03 18:03   ` Ozan Yigit
2001-12-03 20:51     ` Mike Haertel
2001-12-03 10:10 ` north_
2001-12-03 16:55   ` John S. Dyson
2001-12-05  9:56   ` Douglas A. Gwyn

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=20011204172744.411EF3F414@quanstro.net \
    --to=quanstro@speakeasy.net \
    --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).