9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Andrew Zubinski <andrew@itc.kiev.ua>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Re: Future of Plan9
Date: Thu, 21 Dec 2000 18:27:39 +0000	[thread overview]
Message-ID: <3A424B38.5ED4ABF6@itc.kiev.ua> (raw)
In-Reply-To: <91ra7i$54s35$1@ID-64718.news.dfncis.de>

> But remember one point: Plan 9 is a system use to serve as a
> distributed system, but a personal computing system. If you like the
> functions provided by those fancy OSes, by all means change back to it. We
> enjoy Plan 9 as it is simple, easy to use (is it really easy for beginners

What the nice style to help to beginners...

There was  my question/proposition about the cheap non-x86 hardware for Plan9
terminal (and portable POSIX implementation of cpu/file servers). Now I'm
finished the prototype PCB for such beast (133 MHz 64-bits IDT Embedded Orion,
128 MB of DRAM with some fancy features).  But I change my mind and decide to
implement microkernel based Oberon instead Plan9. Why ?

(It is my point of view and, please, don't blame me.)

If you are not a computer scientist - purist you'll need an OS with the highly
balanced design, firstly - with simple but feature rich API. Why? Cause you'll
never find enough time for learning all thouse bang'n'whistles things like
MFC/Motif/CDE/GTK/Gnome/Qt/KDE... . But some features are really needy like
graphics subsystem for data visualization (does anybody really like to read a
500 MB datafile with simulation results?) and with enough interactivity (o'k,
you can write script which will generate postscript from datafile, then render
ps and view it, but how to change one or more values in this "small" source
datafile?).

What I like in Plan9 design are "components as fileservers" conception and
Oberon-like Acme. But there are too many Unix garbage in system design at user
level - unstructured man pages set, obsolete formats, nothing-new shell,
nothing-new utilities set, C compiler only (and nowbody even don't think about
the possibility of porting something like Objective-C preprocessor and runtime
- sorry, I'm trying, but under the work pressure have no time).

As the result instead personal one-box Unix with TeX (or Lout), Octave,
Ghostscript, gv, and what-you-want-how-you-want else, you'll have an equal
personal 3-box Plan9 network with... oh, yes, TeX, Ghostscript,
something-like-gv and what-you-can-port-with-APE. And the real power of Plan9
are used for nothing - for the Unix emulation. Who really need this "feature"
when we have somewhere ugly but stable and very tunable well-documented Unix ?

This disbalance between clean and clever ideas on system level and wrong target
for common OS design (to build distributed Unix) IMHO is the greatest weakness
of Plan9. From the system programmer point of view Plan9 is the great OS, from
the application programmer point of view it is even more ugly than Unix. Maybe
I'm wrong but I can't see any native Plan9 programm oriented to any
non-computer application area where possibilities of Plan9 are usefull (like
distributed CAD/EDA, GIS). And system is not too young...

So, when I see such posts where somebody tolds us that "it is easy to use" or
"change back to other OS", I want to ask: "But how are you using it ? What are
you doing with it ? What is your application area ?".


  reply	other threads:[~2000-12-21 18:27 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-13 10:49 [9fans] " Stephen Adam
2000-12-14  9:49 ` [9fans] " Deztroyer-a1
2000-12-14 12:05   ` Boyd Roberts
2000-12-19  9:57   ` Randolph Fritz
2000-12-19 16:07     ` vecera
2000-12-20  0:58       ` Steve Kilbane
2000-12-20 18:59         ` William Staniewicz
2000-12-21  9:44           ` Alexander C. Deztroyer
2000-12-21 18:27             ` Andrew Zubinski [this message]
2000-12-21  9:45         ` vecera
2000-12-22  0:04           ` Steve Kilbane
2000-12-20  9:59       ` Alexander C. Deztroyer
2000-12-20 10:00       ` Patrick R. Wade
2000-12-20  9:59     ` Alexander C. Deztroyer
2000-12-19 10:48 forsyth
2000-12-21 17:46 anothy
2000-12-23 13:21 ` Steve Kilbane
2000-12-24  1:21   ` Boyd Roberts
2001-01-02 17:52     ` Chris Locke
2000-12-21 18:25 forsyth
2000-12-21 18:30 Russ Cox
2000-12-21 18:33 ` matt
2000-12-21 19:20 forsyth
2000-12-22  9:20 ` cLIeNUX user
2000-12-21 19:21 forsyth
2000-12-21 20:48 ` matt
2000-12-22 11:32 forsyth
2001-01-02 17:24 ` cLIeNUX user
2000-12-22 14:00 forsyth
2000-12-22 22:13 ` Boyd Roberts
2000-12-23 14:40 rob pike
2000-12-24  1:51 Russ Cox
2000-12-24  1:55 ` Boyd Roberts
2000-12-24  2:03 ` Boyd Roberts
2001-01-02 16:51 ` Dan Cross
2000-12-24  2:11 Russ Cox
2000-12-24  2:18 ` Boyd Roberts
2000-12-24 15:46   ` matt heath
2000-12-25  5:47 ` Anthony Starks
2001-01-02 17:36 ` Randolph Fritz
2001-01-02 17:36 ` cLIeNUX user
2001-01-02 17:42 ` Anssi Porttikivi
2001-01-03  1:19 William Staniewicz
2001-01-02 22:43 ` matt heath
2001-01-08  9:54 ` Ross Evans
2003-02-10 17:01 [9fans] " Jaytee
2003-02-11  9:30 ` [9fans] " Douglas A. Gwyn
2003-02-11 13:06   ` Jim Choate
2003-02-11 13:19     ` Russ Cox
2003-02-11 13:32       ` Jim Choate
2003-02-11 14:11     ` Fco.J.Ballesteros
2003-02-12  4:31       ` Jim Choate
2003-02-12  5:12         ` Andrew
2003-02-12 10:34         ` matt
2003-02-12 11:46           ` Digby Tarvin
2003-02-12 17:17         ` Sam
2003-02-12 20:58           ` adrian Damn it !
2003-02-12 21:00             ` Matt Keeler
2003-02-11 14:35     ` Ronald G. Minnich
2003-02-11 16:04     ` Dan Cross
2003-02-11 17:05       ` matt
2003-02-12  9:52     ` ozan s yigit
2003-02-12 18:23   ` north_
2003-02-11 15:01 bwc
2003-02-12  0:42 okamoto
2003-02-12 21:10 bwc

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=3A424B38.5ED4ABF6@itc.kiev.ua \
    --to=andrew@itc.kiev.ua \
    --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).