9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: dhog@plan9.cs.su.oz.au dhog@plan9.cs.su.oz.au
Subject: [comp.os.linux.misc] Help wanted, Plan9 a piece of junk!
Date: Tue, 22 Aug 1995 07:25:18 -0400	[thread overview]
Message-ID: <19950822112518.B3sLbu4ars_TBcZ3MrbbWmrNDNUiAIg7HCN0RzRCsyg@z> (raw)

avg@postman.ncube.com (Vadim Antonov) writes:
>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.

The only problem is that you need an infinite amount of storage.
A "functionally complete" system must be able to understand all
the file formats of the world (audio, video, data compression, MS
Word documents etc) including ones yet to be devised.  It must
contain all the applications that anyone ever wants to be able to
use a computer for, including ones yet to be devised.  No system
can provide all the functionality that users are going to want.

Look at X windows.  It is a system which _tries_ to be functionally
complete.  Yet every new release provides yet another batch of ugly
features that were "missing" in the last.  The toolkit & widget sets
try to do everything for the programmer, who is forced to spend
hours writing messy code which describes just what the widgets
should do, only to find that some bug in the libraries takes even
longer to find a workaround for.  This pattern is duplicated by many
other software systems, written by well meaning programmers
with your philosophy.

So Seventh Edition Unix didn't provide support for networking.
Can't really blame its authors, networking was pretty non-existant
in those days.  I suppose that in another 10-20 years, people like
you will be bemoaning the fact that the original versions of Plan 9
didn't include support for (say) direct brain interfaces, so that there
are multiple conflicting implementations of them...






             reply	other threads:[~1995-08-22 11:25 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1995-08-22 11:25 dhog [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  6:18 Vadim
1995-08-21 22:54 forsyth
1995-08-21  4:59 Vadim
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=19950822112518.B3sLbu4ars_TBcZ3MrbbWmrNDNUiAIg7HCN0RzRCsyg@z \
    --to=dhog@plan9.cs.su.oz.au \
    /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).