From: Karl Dahlke <eklhad@home.com>
To: blinux-list@redhat.com
Subject: Windows, Linux
Date: Sat, 8 Sep 2001 12:18:07 -0700 [thread overview]
Message-ID: <20010908191806.VASR557.femail15.sdc1.sfba.home.com@eklhad> (raw)
Just one brief thought on the Windows Linux discussion,
which I've mostly tried to stay out of.
I've seen my wife, an intelligent woman who has been to college,
and has two good eyes, spend half a day trying to install a game for
our children. Finally she gives up in despair and writes off the $20.
Her time is just too precious. Maybe the next game will install properly.
And I've seen her install one game and have it break another one.
Together we tried to unbreak that other game, cuz we really liked it,
and we tried off and on for over a year, then gave up.
One day she installed a third game, and if fixed the first game.
We still don't know why.
Windows is so monolythic and intertwined, the slightest bug or inconsistency
or incompatibility can break six other things, or even bring Windows to its knees.
It's terrible!
Compare this with the simple beauty of rpm -i, which works like a dream.
So Linux is better, right?
Maybe not.
If she had Linux, and was facing a $ prompt, she'd have no idea what to do.
Even if I told her to type rpm -i, and then explained all the wherefores and
why's of becoming root, with passwords, and now rpm -i works,
but she's still looking at a $ prompt.
"So, how do I run the game?" she asks.
Well I tell her about how to get info about the package she just loaded,
and a list of the associated files,
which you cull through looking for something in /usr/bin,
and there's the command to run.
Then run "man command" to read ten pages of options and arguments,
and oh it looks like you'll have to make a .commandrc file
in your home directory with lots of options and settings,
and ok, now you can play your game.
Yeah, like that's really a user friendly system!
For her at least, Linux is terrible!
And there we are: two powerful operating systems that are almost
unusable by anyone except geeks.
All this has nothing to do with blinux I suppose,
and perhaps I shouldn't have posted it,
except to say that nothing really changes if you're blind.
Both systems are still hard to use, for all the same reasons,
but they become even harder, because you have to do
everything through an adapter.
Now I love Linux, but then again, I'm a geek.
And perhaps that's another salient point for this group.
Sighted users can sometimes brouse the net and get mail
on Windows,
even install and play a few games if they're very lucky,
all without any computer expertise.
(This also assumes our casual home user buys a new computer every two years,
or nothing works.)
Blind users don't have this luxury.
We *must* become geeks, to manage these complex adapters and synthesizers etc,
and once you've acccepted this reality, and become a geek,
I think you'll like Linux too,
for the same reasons I do.
Or, maybe you'll become an even bigger geek than I,
and you'll understand why those three games have inconsistent versions of the same dll,
and how to make them all work together.
Who can tell.
Karl
next reply other threads:[~ UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
Karl Dahlke [this message]
` Windows, Linux (please don't make this an os-war) Andor Demarteau
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=20010908191806.VASR557.femail15.sdc1.sfba.home.com@eklhad \
--to=eklhad@home.com \
--cc=blinux-list@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).