9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Quinn Dunkan <quinn@chunder.ugcs.caltech.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Private Namespaces for Linux
Date: Mon, 26 Nov 2001 18:22:57 -0800	[thread overview]
Message-ID: <20011127022302.233B2781C8@chunder.ugcs.caltech.edu> (raw)
In-Reply-To: Your message of "Tue, 27 Nov 2001 13:13:44 +1300." <3.0.6.32.20011127131344.0097d458@pop3.clear.net.nz>


> > intellectual inertia
> > satisfaction with the status quo
> > following the crowd
> > listening to the people who shout the loudest
> > fashion
> > no integrated web browser/mail reader/nntp client/html wysiwyg editor
> >
> I hesitate to use the "M" word around here, but from my perspective the
> absence of anything like MS Excel, Word, and Access is a big disincentive.

I was sort of under the impression that the sort of people who would have fun
with Plan 9 are those who already have more fun with TeX or lout than Word.
Could be wrong, though.

> Also maybe the absence of any books doesn't help visibility. Something like
> "The Plan 9 Programming Environment" would be welcome.

As far as programming in C goes, I think plan 9 is actually better off than
unix or windows with their large bookshelves.  From my point of view:

The best kind of documentation is that which doesn't need to be there.  Plan 9
lacks a lot of historical cruft and spiky pit traps that need documentation
under, say, unix.  The documentation that is there is easy to find and
download and read on the screen or print out if desired, or can even be bought
in hard copy.  This is more flexible than a paper book which only has the last
option.  And lastly (and not leastly), the source is there, and easy to find,
and relatively free of ifdefs and cross-platform special cases and accumulated
toejam.

The situation is less good if C happens to not be your favorite language, but
people who use "minority" languages usually face the same sort of "write it
yourself, then" issues that people who use minority OSes face.


  parent reply	other threads:[~2001-11-27  2:22 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-26  5:31 David Gordon Hogan
2001-11-26 10:00 ` Thomas Bushnell, BSG
2001-11-26 10:48   ` Matt
2001-11-26 14:29     ` Ronald G Minnich
     [not found]     ` <Pine.LNX.4.33.0111260728070.16611-100000@snaresland.acl.la nl.gov>
2001-11-27  0:13       ` Andrew Simmons
2001-11-27  1:37         ` Ronald G Minnich
     [not found]         ` <Pine.LNX.4.33.0111261834400.19833-100000@snaresland.acl.la nl.gov>
2001-11-27  2:17           ` Andrew Simmons
2001-11-27  2:28             ` Boyd Roberts
2001-11-27  2:46               ` Andrew Simmons
2001-11-27 11:53             ` Ralph Corderoy
2001-11-27  2:22         ` Quinn Dunkan [this message]
2001-11-27  2:54           ` Andrew Simmons
2001-11-27  3:06             ` Boyd Roberts
2001-11-26 14:18 ` Ronald G Minnich
2001-11-26 18:26   ` Dan Cross
  -- strict thread matches above, loose matches on Subject: below --
2001-11-27  8:49 nigel
2001-11-27  7:24 nigel
2001-11-27  6:43 David Gordon Hogan
2001-11-27  3:09 Russ Cox
2001-11-27  8:13 ` Skip Tavakkolian
2001-11-27  3:03 geoff
2001-11-26 18:27 erik quanstrom
2001-11-22  0:42 rob pike
2001-11-22  0:36 rob pike
2001-11-21 23:02 rob pike
2001-11-21 23:26 ` Matt
2001-11-21 20:08 erik quanstrom
2001-11-21 16:49 forsyth
2001-11-21 14:52 presotto
2001-11-21 20:12 ` Dan Cross
2001-11-21 20:48 ` Skip Tavakkolian
2001-11-21 22:50   ` Andrew Simmons
2001-11-25 15:23   ` david presotto
2001-11-25  4:19     ` George Michaelson
2001-11-21  3:02 Eric Grosse
2001-11-21  1:29 okamoto
2001-11-21  3:46 ` Ronald G Minnich
     [not found] ` <Pine.LNX.4.33.0111202037460.14857-100000@snaresland.acl.la nl.gov>
2001-11-21 17:51   ` Skip Tavakkolian
2001-11-21 22:44     ` Ronald G Minnich
2001-11-21  0:03 David Gordon Hogan
2001-11-20 23:48 forsyth
2001-11-20 23:40 David Gordon Hogan
2001-11-20 23:45 ` Alexander Viro
2001-11-20 23:54 ` Matthew Hannigan
2001-11-21 17:24 ` Thomas Bushnell, BSG
2001-11-22  9:56 ` Thomas Bushnell, BSG
2001-11-20 22:54 David Gordon Hogan
2001-11-20 23:17 ` Ronald G Minnich
2001-11-20 23:49   ` Matthew Hannigan
2001-11-20 23:31 ` Alexander Viro
2001-11-20 22:40 David Gordon Hogan
2001-11-20 22:47 ` Ronald G Minnich
2001-11-20 23:29 ` Alexander Viro
2001-11-20 22:20 presotto
2001-11-20 22:08 David Gordon Hogan
2001-11-20 23:40 ` Dan Cross
2001-11-21 15:05 ` Boyd Roberts
2001-11-20 22:05 erik quanstrom
2001-11-20 21:24 David Gordon Hogan
2001-11-20 21:49 ` Ronald G Minnich
2001-11-20 20:54 presotto
2001-11-20 20:49 David Gordon Hogan
2001-11-20 20:57 ` Ronald G Minnich
2001-11-21  5:59   ` Taj Khattra
2001-11-20 10:22 forsyth
2001-11-19 21:46 [9fans] vmware Russ Cox
2001-11-19 23:59 ` [9fans] Private Namespaces for Linux Matt
2001-11-20  5:26   ` Ronald G Minnich
2001-11-20 17:28   ` Thomas Bushnell, BSG
2001-11-20 20:46     ` Ronald G Minnich
2001-11-20 21:08       ` Alexander Viro
2001-11-20 21:48         ` Ronald G Minnich
2001-11-20 22:28           ` Ronald G Minnich
2001-11-20 23:14             ` Alexander Viro

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=20011127022302.233B2781C8@chunder.ugcs.caltech.edu \
    --to=quinn@chunder.ugcs.caltech.edu \
    --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).