From: newsham@lava.net (Tim Newsham)
Subject: [TUHS] UNIX as literature
Date: Sun, 11 Jun 2006 06:18:36 -1000 (HST) [thread overview]
Message-ID: <Pine.BSI.4.61.0606110615550.20225@malasada.lava.net> (raw)
In-Reply-To: <00c101c68bb9$bd7f6050$4205a6c0@FERRARI>
> This reminded me of a time not so long ago when I was seated in Starbucks in
> Menlo Park enjoying my Caramel Macchiato Venti and overhearing a heated
> debate between 6 or 7 guys about the GUI vs. command line issue. It seemed
> to start when a couple of guys in one party, seemingly unknown to the other
> party, who were talking about kde, rudely butted in to their conversation.
> Anyway the debate got so verbal that in the end they were all ushered out of
> Starbucks in an effort to keep the peace. How funny it was.
The bandwidth of a mouse and menus is not very high. The bandwidth of a
keyboard is a lot higher. Going the other way, though, the bandwidth of
graphical data is much higher than textual data (perhaps as high
as a thousand words per picture).
> Berny
Tim Newsham
http://www.lava.net/~newsham/
next prev parent reply other threads:[~2006-06-11 16:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.364.1149808191.1130.tuhs@minnie.tuhs.org>
2006-06-09 11:42 ` bgoodheart
2006-06-09 12:42 ` Milo Velimirovic
2006-06-11 16:18 ` Tim Newsham [this message]
2006-06-12 1:22 ` Wesley Parish
2006-06-09 12:41 Norman Wilson
-- strict thread matches above, loose matches on Subject: below --
2006-06-08 6:06 Wolfgang Helbig
2006-06-08 6:20 ` Lyrical Nanoha
2006-06-08 17:08 ` Gregg C Levine
2006-06-08 19:41 ` Michael Parson
[not found] <447E9540.2020003@io.dk>
[not found] ` <200606011357.11990.aren.tyr@gawab.com>
[not found] ` <447F0062.8060302@daleco.biz>
[not found] ` <447F4E7C.8050404@bitfreak.org>
[not found] ` <20060603195531.3c634eca@hydrocodone.org>
2006-06-08 3:11 ` Greg 'groggy' Lehey
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.BSI.4.61.0606110615550.20225@malasada.lava.net \
--to=newsham@lava.net \
/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).