From pycyn@aol.com Tue Aug 22 18:22:01 2000
Return-Path: <Pycyn@aol.com>
Received: (qmail 11809 invoked from network); 23 Aug 2000 01:22:00 -0000
Received: from unknown (10.1.10.27) by m4.onelist.org with QMQP; 23 Aug 2000 01:22:00 -0000
Received: from unknown (HELO imo-r10.mx.aol.com) (152.163.225.10) by mta2 with SMTP; 23 Aug 2000 01:22:00 -0000
Received: from Pycyn@aol.com by imo-r10.mx.aol.com (mail_out_v27.12.) id a.e6.9f71c9e (4235) for <lojban@egroups.com>; Tue, 22 Aug 2000 21:21:50 -0400 (EDT)
Message-ID: <e6.9f71c9e.26d4812e@aol.com>
Date: Tue, 22 Aug 2000 21:21:50 EDT
Subject: Re: [lojban] emacs etc.
To: lojban@egroups.com
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: AOL 3.0 16-bit for Windows sub 41
From: pycyn@aol.com

In a message dated 00-08-22 16:01:46 EDT, jewel writes:

<< It's a myth to think that Word is user-friendly. It is probably easier to
use for those who can't "read" (ie read documentation) but otherwise it's
a very complex piece of machinery (more so than Emacs). >>

Depends on what you mean. Word may be very complex in some ways, but I can 
take it out of the box and get acceptable results knowing no more than basic 
typing skills. Admittedly its Help files suck, since they never call 
anything by the name I use for it, but I can usually get around to whatever I 
want eventually. The important point is that I can't use emacs until after 
that 2 hours of training and then I still have the hassle to get to those odd 
special cases. In other words, real people don't -- and don't want to have 
to -- read documentation. Nor ought they be asked or expected to for 
standard functions (why ALL programming languages suck). And those are the 
users to be friendly to.

