From: Boyd Roberts <boyd@prl.dec.com>
To: rc@archone.tamu.edu
Subject: Re: access
Date: Tue, 6 Aug 1991 07:11:41 -0500 [thread overview]
Message-ID: <9108061411.13660.rc.baduj@prl.dec.com> (raw)
In-Reply-To: <9108021515.AA12845@milton.u.washington.edu>
Donn Cave <donn@milton.u.washington.edu>
Efficiency is "not the issue" only when the program in question doesn't play
a significant role in your computing environment.
Hmm, I've just booted up my fave old tube computer, complete with mercury
delay lines. But, dammit! rc is just too slow. All those memory accesses!
All that executable code! Time to implement test(1) with some of these handy
valve diodes, or I'll never get to login before Christmas.
Now, just where did I put my soldering iron?
next prev parent reply other threads:[~1991-08-06 12:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1991-08-02 15:15 access Donn Cave
1991-08-06 12:11 ` Boyd Roberts [this message]
-- strict thread matches above, loose matches on Subject: below --
1991-08-01 19:36 access Donn Cave
1991-08-01 19:49 ` access Hamish Macdonald
1991-08-02 8:29 ` access Boyd Roberts
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=9108061411.13660.rc.baduj@prl.dec.com \
--to=boyd@prl.dec.com \
--cc=rc@archone.tamu.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).