From: FODEMESI Gergely <fgergo@eik.bme.hu>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Put (was: [9fans] acme: some thoughts about design)
Date: Sun, 30 May 2004 01:10:01 +0200 [thread overview]
Message-ID: <Pine.GSO.4.58L0.0405300051550.21346@goliat> (raw)
In-Reply-To: <d9e7bab009b153c675bc3dfd7ff54f48@9netics.com>
On Sat, 29 May 2004 9nut@9netics.com wrote:
> > Don't use files ;-) It is a computer task to save my input but
> > I dont understand why I must tell the computer where to store.
Even in 1997 I met people who thought, that a user should not be obliged
to know when, where and what to save or that the concept of saving should
exist at all. (A real visionary might have thought about this probably
decades ago.)
> Obviously a failure of vision on Rob's part!
Put might have come from an idea like above (ie. "save" is not the best
way to express the real need), or it was just shorter than "Save".
gergo
prev parent reply other threads:[~2004-05-29 23:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-28 9:01 [9fans] acme: some thoughts about design cej
2004-05-29 9:28 ` Matthias Teege
2004-05-29 14:48 ` Russ Cox
2004-05-29 16:18 ` Matthias Teege
2004-05-29 18:31 ` 9nut
2004-05-29 23:10 ` FODEMESI Gergely [this message]
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=Pine.GSO.4.58L0.0405300051550.21346@goliat \
--to=fgergo@eik.bme.hu \
--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).