9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: dave.l@mac.com
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] 8c "out of fixed registers"
Date: Tue, 20 Nov 2007 22:58:17 +0000	[thread overview]
Message-ID: <456C40B6-9099-43C7-A83E-C9927F1640EC@mac.com> (raw)
In-Reply-To: <d1c554290711200728y617a57c9s2662a2c56fe35a6e@mail.gmail.com>

> may I suppose you use a web browser?

You may.

> if yes, is this complexity needed or not?

No it is not, because the browser is not "needed".
Neither is OS X or the MacBook upon which they run.

AFAIK the only things we _need_ are:
air, food, water, shelter and reproduction (have I missed any?):
all the rest is choice.

Just because someone choses to use some piece of unnecessarily  
complex technology
does not make it a "need", it makes it a "want".

We don't need web browsers, video players etc.:
we just like having them.

If you then say "I need it to do my job",
then I say that the job is your choice (as is mine using linux etc.),
and so ad infinitum.

If the government mandates use of a web browser,
well, we voted for them, right?
If you don't fight tooth and nail against them then it's your choice.

In other words, I use the shit, reluctantly,
I don't increase the size of the pile.
While I'm not happy with the situation,
as least I'm not exacerbating it.

Plan9 with a usable web browser would be a fine idea.
Unfortunately, the pain and complexity that goes
with making that fine idea into a reality would drive people away  
from plan9.

D.


  parent reply	other threads:[~2007-11-20 22:58 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-19  4:12 Federico G. Benavento
2007-11-19  9:32 ` [9fans] Fwd: " Federico Benavento
2007-11-19 17:45 ` [9fans] " erik quanstrom
2007-11-19 18:14   ` Charles Forsyth
2007-11-19 18:13     ` Federico G. Benavento
2007-11-19 18:37       ` Charles Forsyth
2007-11-19 18:48         ` Robert William Fuller
2007-11-19 19:14           ` Charles Forsyth
2007-11-19 19:21             ` Charles Forsyth
2007-11-19 20:38           ` Uriel
2007-11-19 21:08             ` Iruata Souza
2007-11-20  0:20               ` dave.l
2007-11-20  3:54                 ` Bruce Ellis
2007-11-20 15:28                 ` Iruata Souza
2007-11-20 16:39                   ` David Leimbach
2007-11-20 16:48                     ` Iruata Souza
2007-11-20 17:05                       ` David Leimbach
2007-11-20 17:29                         ` Anthony Sorace
2007-11-22 10:17                         ` Douglas A. Gwyn
2007-11-22 12:24                           ` erik quanstrom
2007-11-20 22:58                       ` dave.l
2007-11-21  1:11                         ` Iruata Souza
2007-11-20 22:58                   ` dave.l [this message]
2007-11-21 16:15                     ` Uriel
2007-11-26 10:30                       ` Douglas A. Gwyn
2007-11-19 22:05           ` erik quanstrom
2007-11-19 20:00     ` Bruce Ellis
2007-11-19 22:18       ` Charles Forsyth
2007-11-19 18:18 ` Charles Forsyth
2007-11-19 18:32   ` Federico G. Benavento

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=456C40B6-9099-43C7-A83E-C9927F1640EC@mac.com \
    --to=dave.l@mac.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).