From: Ram'on Garc'ia Fern'andez <ramon.n.0.spam@n0.spam.juguete.quim.ucm.es.sim.ucm.es>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Essay: Is network transparency something bad?
Date: Fri, 25 Oct 2002 12:08:59 +0000 [thread overview]
Message-ID: <apb64d$fkp$1@crispin.sim.ucm.es> (raw)
In-Reply-To: <0beaa8f299b645c6f9a31874ba08c7db@plan9.bell-labs.com>
Russ Cox wrote:
>
> - people do stupid things with x
> - let's not anyone do x
>
> and the fallacy is that if you know what you're doing
> it's very useful to do x. Why tie your own hands behind
> your back just so that people have to find some other
> way to do stupid things?
>
Though I do not agree entirely with the essay, I think that
he has a point.
It would be nice if Plan9 interfaces were extensible, so that, say, when
a file belongs to a filesystem mounted over a network the application
reading the file could receive optional events regarding availability,
progress of the operation, and so on.
Ramon
next prev parent reply other threads:[~2002-10-25 12:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-24 17:08 Russ Cox
2002-10-24 17:16 ` John Saylor
2002-10-25 11:44 ` Boyd Roberts
2002-10-25 12:08 ` Ram'on Garc'ia Fern'andez [this message]
2002-10-25 13:31 ` Boyd Roberts
-- strict thread matches above, loose matches on Subject: below --
2002-10-25 7:24 Fco.J.Ballesteros
2002-10-24 21:49 Skip Tavakkolian
2002-10-25 2:04 ` paurea
2002-10-24 17:54 rog
2002-10-24 18:40 ` Scott Schwartz
2002-10-24 19:05 ` Ronald G Minnich
2002-10-24 19:25 ` Dan Cross
2002-10-24 19:32 ` Scott Schwartz
2002-10-25 13:10 ` Boyd Roberts
2002-10-24 22:09 ` Steve Kilbane
2002-10-24 16:43 Skip Tavakkolian
2002-10-24 15:51 Ramon Garcia
2002-10-24 17:36 ` Dan Cross
2002-10-25 0:06 ` paurea
2002-10-25 14:40 ` Dan Cross
2002-10-24 15:09 Skip Tavakkolian
2002-10-24 18:58 ` Dan Cross
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='apb64d$fkp$1@crispin.sim.ucm.es' \
--to=ramon.n.0.spam@n0.spam.juguete.quim.ucm.es.sim.ucm.es \
--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).