9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: forsyth@plan9.cs.york.ac.uk forsyth@plan9.cs.york.ac.uk
Subject: [comp.os.linux.misc] Help wanted, Plan9 a piece of junk!
Date: Sat, 19 Aug 1995 09:32:36 -0400	[thread overview]
Message-ID: <19950819133236.oq8-C_2Ll4DegcqoFzX5JAFY3EQubkieSwK1FqPwI8M@z> (raw)

several people have commented on the reliability of the system.
it is wrong to conclude from installation problems (or even some
operational problems on the PC) that plan 9 is an `alpha' or
`early version' of something, and that it is unsurprising to have it
fail regularly.  once installed on (or adapted to) a particular hardware
configuration, most of the software that is running is software with
a good few years behind it.  the bulk of the code is portable code
that has run on many different platforms, not just the PC.
it certainly is not error free, but it is far better than `alpha' or `beta' quality.

of course, there are newer, more experimental parts, that
are less well tried, but as in the original Unix systems,
the documentation is forthright about potential problems and limitations.

as one example, see the health warnings in the documentation
for Mothra and the Panel library on which it is built.
nevertheless, i've been using the Panel library
in a program i'm building and i regret to say that the errors have
been in my code, not td's.  (it is a very nice package, by the way.)

in general, compared to most other systems i know, there is typically several orders of magnitude less
source code to do more work (and more interesting work at that),
and consequently there is less space for the bugs to hide.

you really do have to read the documentation, though.
if you approach the system with too many preconceptions about what
it `obviously' will do, it will trip you up.  in particular,
the PC is just a hardware platform on which Plan 9 runs.
it isn't the system's primary platform (it hasn't got one!).

Plan 9 has its own conventions that it adheres to on *all hardware
platforms*.  this is a strength, not a weakness.
as someone operating a plan 9 installation, i can tell you from
experience that it is a real joy to have something that is so
plug compatible in its interfaces and details of management
that i can once again regard sparcs, 680x0 boxes, PCs, etc. as
just a source of faster (or slower) computing power.






             reply	other threads:[~1995-08-19 13:32 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1995-08-19 13:32 forsyth [this message]
  -- strict thread matches above, loose matches on Subject: below --
1995-08-25  6:28 dhog
1995-08-25  4:14 Johnson
1995-08-24  8:49 dhog
1995-08-24  7:27 Johnson
1995-08-23 15:13 Victor
1995-08-22 11:25 dhog
1995-08-22  6:18 Vadim
1995-08-21 22:54 forsyth
1995-08-21  4:59 Vadim
1995-08-19  5:03 pete
1995-08-16 21:16 Scott
1995-08-16 14:42 Steve_Kilbane
1995-08-16  6:39 dhog
1995-08-16  5:45 dhog
1995-08-16  1:12 forsyth
1995-08-15 16:00 Bill
1995-08-15 15:24 presotto
1995-08-15 14:53 Greg
1995-08-15 13:29 jmk
1995-08-15 13:28 Ture
1995-08-15 12:38 David
1995-08-15 10:29 dhog
1995-08-14 21:46 Bill

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=19950819133236.oq8-C_2Ll4DegcqoFzX5JAFY3EQubkieSwK1FqPwI8M@z \
    --to=forsyth@plan9.cs.york.ac.uk \
    /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).