9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Vadim Antonov avg@postman.ncube.com
Subject: [comp.os.linux.misc] Help wanted, Plan9 a piece of junk!
Date: Mon, 21 Aug 1995 00:59:02 -0400	[thread overview]
Message-ID: <19950821045902.Y-aLskl3n89FMSwejmU7rEQev79Bs9hgSj3lCMUtdWM@z> (raw)

>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.

Is it anything new?  My first large-scale project (i was in a kind
of leading position in the project, it had no formal "organization"
behind it for a long time) was building a family of Unix-like systems
(called DEMOS, addreviation for "Interactive Unified Portable Operating
System").  It was running on eight different architectures (including
clones of IBM/370 and some machines with no Western prototypes), and
was built from the same source tree (modulo hardware dependencies and
stuff like support for 3270s).  Needless to say all machines were
"the same".  It also was (and still is) the only effort in complete
internationalization of Unix.

I guess it is more like that Plan 9 has a single organization
producing releases.  If the system will be successful it is
inevitably going to change as i do not suppose that Bell Labs
people will be interested in supporting the commercial releases
(it is a hell lot of tedious work).

When it will happen the history with Unix will repeat itself,
as the root cause of the divergence of revisions wasn't fixed.
That root cause is the functional incompleteness.  Nobody in 
his own mind makes systems incompatible for the sheer hell of it.
Rather, people add things to fix their particular problems which
weren't adequately addressed in the original system.

The ideal system is "functionally complete" in regard to the
class of applications.  Then there wouldn't be ugly extensions
and creeping featurism.  Note that this approach is kind of
contradictory to the pure minimalism, which is to do absoulte
minimum to solve the problems at hand.

--vadim






             reply	other threads:[~1995-08-21  4:59 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1995-08-21  4:59 Vadim [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-19 13:32 forsyth
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=19950821045902.Y-aLskl3n89FMSwejmU7rEQev79Bs9hgSj3lCMUtdWM@z \
    --to=9fans@9fans.net \
    /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).