From: "Erik Jessen" <ejessen@adelphia.net>
To: "'Feneric Brown'" <feneric@saugus.net>, <xconq7@sources.redhat.com>
Subject: RE: HW requirements
Date: Sun, 11 Jan 2004 17:02:00 -0000 [thread overview]
Message-ID: <000b01c3d865$e91cc860$6401a8c0@Win2k> (raw)
In-Reply-To: <EB02CD3D-4455-11D8-910E-000393439120@saugus.net>
Feneric,
Thanks! I know people who do ASCII-only for email, etc. because they
either have a slow connection, or want to avoid viruses. I'd expected
that for playing Xconq, they'd have to have newer hardware (and/or a
fast connection) to play Xconq, simply because of RAM/CPU
considerations.
This is really interesting.
Erik
-----Original Message-----
From: xconq7-owner@sources.redhat.com
[mailto:xconq7-owner@sources.redhat.com] On Behalf Of Feneric Brown
Sent: Sunday, January 11, 2004 8:48 AM
To: xconq7@sources.redhat.com
Subject: RE: HW requirements
> How many people use VT100 any more?
You'd be surprised. I do the maintenance at a company that provides a
number of shell accounts to customers. The users typically fall into
one or more of the following groups:
1. Sophisticated users / designers who want a decent UNIX-like
environment with fairly up-to-date tools without having to maintain it
or handle the updating themselves;
2. Users who are blind and have all output redirected through either a
reader box or a Braille hand reader;
3. Users who are opposed to the upgrade cycle and who (often for
philosophical as well as financial reasons) have chosen to freeze their
hardware at a certain level that handles their own requirements (the
C128 is popular, but there are other makes & models that are also
used);
4. Sophisticated users who choose to route all their e-mail through a
system including combinations of things like Procmail, SpamAssassin,
JunkFilter, TMDA, Pine, Mutt, etc. in order to largely sidestep the
issues of spam and virii that so plague the modern world.
We maintain a bunch of games on the system, and I'd have to say that
Cconq (the VT100 version of Xconq) remains one of the most popular,
right up there with NetHack and the various IF titles.
next prev parent reply other threads:[~2004-01-11 17:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-11 16:48 Feneric Brown
2004-01-11 17:02 ` Erik Jessen [this message]
2004-01-13 10:42 ` Bruno Boettcher
-- strict thread matches above, loose matches on Subject: below --
2004-01-13 15:59 Eric W. Brown
2004-01-11 18:12 Eric W. Brown
2004-01-12 17:19 ` Eric McDonald
2004-01-11 18:10 Feneric Brown
2004-01-11 20:05 ` Jim Kingdon
2004-01-11 16:52 Feneric Brown
2004-01-10 17:57 New Action: change-type Hans Ronne
2004-01-10 18:59 ` HW requirements Erik Jessen
2004-01-10 19:44 ` Hans Ronne
2004-01-10 23:31 ` klaus schilling
2004-01-11 0:25 ` Erik Jessen
2004-01-11 3:44 ` Jim Kingdon
2004-01-11 7:25 ` Erik Jessen
2004-01-11 7:45 ` Eric McDonald
2004-01-11 7:52 ` Erik Jessen
2004-01-11 21:19 ` Jim Kingdon
2004-01-11 0:31 ` Hans Ronne
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='000b01c3d865$e91cc860$6401a8c0@Win2k' \
--to=ejessen@adelphia.net \
--cc=feneric@saugus.net \
--cc=xconq7@sources.redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).