9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Dave Lukes <davel@anvil.com>
To: 9fans <9fans@cse.psu.edu>
Subject: Re: [9fans] insularity
Date: Wed, 17 Mar 2004 17:43:03 +0000	[thread overview]
Message-ID: <1079545383.14420.651.camel@zevon> (raw)
In-Reply-To: <286242286f27.286f27286242@cwru.edu>

> When you pit this mastery against the sense of entitlement  that comes
> from mainstream systems you get conflicts like this. People expect
> canned solutions not pointers to *how* to solve things.

Yes, and maybe we should emphasise this more.

Personally, I feel that if people don't "get it",
then maybe that's their problem?

> The real issue is how to solve this problem. 

Well, to some extent it solves itself ...

If people aren't willing to invest the effort,
then they don't get the benefit.

Remember, I'm in a far worse position than a lot of 9fans:
I have no plan9 system, but nonetheless, I think I "get it".

> I propose that we emphasize the tools philosophy to clarify the underlying philosophy and justifications in introductions to new users. It's already there really, but scattered in other explanations rather than dealt with systematically. 

Well, OK, but I would have thought that was a "given" ...

> One way of solving this would be to use existing books like the 
>  "Unix Programming Environment" or "Software Tools" with their code updated for Plan 9. I think a lot of people avoid those books because they don't believe they need to learn ancient Unix or Ratfor. And it's a shame because they miss the conceptual forest for the trees of individual system implementations and cruft. 

> I'll gladly contribute anything I can if we can agree on a roadmap.

Well, I still think that,
since I "get it" with the available information, there's no problem!

	Dave.




  parent reply	other threads:[~2004-03-17 17:43 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-17 16:52 Noah Evans
2004-03-17 17:24 ` ron minnich
2004-03-17 17:25 ` andrey mirtchovski
2004-03-17 17:43 ` Dave Lukes [this message]
2004-03-17 17:59   ` rog
2004-03-17 17:58     ` Dave Lukes
2004-03-17 18:19       ` Don Bailey
2004-03-17 18:18         ` David Presotto
2004-03-18  7:23       ` boyd, rounin
2004-03-18  1:05 ` bs
2004-03-18  1:20   ` Taj Khattra
  -- strict thread matches above, loose matches on Subject: below --
2004-03-18  2:08 Noah Evans
2004-03-18  8:14 ` Michael H. Collins
2004-03-17 18:11 Noah Evans
2004-03-17 17:53 Noah Evans
2004-03-17  8:55 [9fans] Novice question - run as other Geoff Collyer
2004-03-17 16:22 ` [9fans] insularity rog
2004-03-17 16:32   ` Aharon Robbins
2004-03-17 16:36   ` suspect
2004-03-17 16:48     ` lucio
2004-03-17 18:09       ` Dave Lukes
2004-03-17 19:26         ` Fco.J.Ballesteros
2004-03-18 13:50           ` Dave Lukes
2004-03-17 22:48         ` Geoff Collyer
2004-03-17 23:11           ` David Presotto
2004-03-18  7:47           ` boyd, rounin
2004-03-18  2:45       ` boyd, rounin
2004-03-17 17:53   ` Dave Lukes
2004-03-17 19:12     ` Latchesar Ionkov
2004-03-17 18:56   ` vdharani
2004-03-18  2:39   ` boyd, rounin

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=1079545383.14420.651.camel@zevon \
    --to=davel@anvil.com \
    --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).