9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Michael H. Collins" <mike@linuxlink.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] insularity
Date: Thu, 18 Mar 2004 02:14:46 -0600	[thread overview]
Message-ID: <40595A76.5010802@linuxlink.com> (raw)
In-Reply-To: <2fa7582fad1f.2fad1f2fa758@cwru.edu>

bobdamn this thread


Noah Evans wrote:
> I'm sorry, I wasn't clear.
> 
> I'm not saying that people can't have a perfectly productive and enjoyable experience in other systems. What I'm saying is that those experiences are essentially impoverished. By necessity in windows and by sufficiency in modern *nix. 
> 
> Think of this analogy, modern operating systems are like eating in restaurants all your life. It's fine if you like the food, but if you ever want something else, because you never learned to cook(linux) or the restaraunt won't let you(windows), you'll be stuck. Or, worse yet, you'll end up building another restaurant to get the food you want, wasting 10 times the effort you would have learned by learning the proper(tool based) way of doing things.
> 
> Noah
> 
> 
> 
> 
> 
> By 
> 
> The difference between rote memorization and understanding. 
> 
> ----- Original Message -----
> From: bs <bs@nospam.com>
> Date: Wednesday, March 17, 2004 8:05 pm
> Subject: Re: [9fans] insularity
> 
> 
>>>But this philosophy is lost on people who are used to the 
>>
>>windows/consumer Unix world because they're used to solutions that 
>>violate the tools method of solving problems. 
>>This is not a fair statement.
>>IMO, the beauty of something is to the builder, the experience of 
>>something is to the user.
>>A porsche driver cares about how it feels to drive, not the 
>>geometry of 
>>the suspension or the degrees of freedom used to tune it.
>>
>>Similary, one can keep the innovations of plan9 under the covers 
>>and 
>>deliver something an end user might enjoy(even if it means tab 
>>completion). (this is from someone who has contributed zippo (other 
>>than 
>>noise) to this list).
>>
>>
> 
> 
> 
> 

-- 
Michael H. Collins  Admiral, Penguinista Navy	
http://linuxlink.com

http://www.gracklenews.com/




  reply	other threads:[~2004-03-18  8:14 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-18  2:08 Noah Evans
2004-03-18  8:14 ` Michael H. Collins [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-03-17 18:11 Noah Evans
2004-03-17 17:53 Noah Evans
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
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
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=40595A76.5010802@linuxlink.com \
    --to=mike@linuxlink.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).