9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: matt@proweb.co.uk
To: 9fans@cse.psu.edu
Subject: Re: [9fans] plan9 finished
Date: Sat, 28 Feb 2004 12:45:29 +0000	[thread overview]
Message-ID: <124b0b2bd6fb1fcc201f7e7ff1d33d5f@juice.thebigchoice.com> (raw)
In-Reply-To: <200402281137.i1SBbabS044383@adat.davidashen.net>

>> When I said I tell people plan9 is finished I mean "complete" not "dead".

>Do you think there is a difference between complete and dead?

I prefer to think of it as stable and predictable.
The kernel is finished modulo drivers. If fairly sure there won't suddenly be a new scheduler or VM or 9p2005 or a bunch of new syscalls to surprise me.

I think people want to be sure in their time investment. If they see that someone is *still* fiddling with the kernel then if they put 6 months into learning the OS http://plan9.bell-labs.com/plan9dist/ will still be there at the end of it.

Personally I'd prefer to think that if I download it today I won't have to be downloading updates every week for the rest of my days that break all my efforts to date.

Personally I would still use plan9 if everyone else stopped, I'm sure plenty of us here feel the same.

m



  reply	other threads:[~2004-02-28 12:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-28 11:30 matt
2004-02-28 11:37 ` David Tolpin
2004-02-28 12:45   ` matt [this message]
2004-02-28 13:00     ` David Tolpin
2004-02-28 13:22       ` David Presotto
2004-02-28 13:36         ` matt
2004-02-28 13:46           ` Brantley Coile
2004-02-28 14:04             ` David Tolpin
2004-02-28 15:11         ` andrey mirtchovski
2004-02-28 16:27           ` David Presotto
2004-02-28 13:27       ` matt
2004-02-28 13:29         ` David Tolpin

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=124b0b2bd6fb1fcc201f7e7ff1d33d5f@juice.thebigchoice.com \
    --to=matt@proweb.co.uk \
    --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).