From: Xah <xahlee@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Emacs usability
Date: Tue, 12 Aug 2008 07:48:58 -0700 (PDT) [thread overview]
Message-ID: <d476bf22-aa9e-45e0-a13d-0f5a9c29e2e3@r35g2000prm.googlegroups.com> (raw)
In-Reply-To: 86r68u5niv.fsf@lifelogs.com
On Aug 12, 7:14 am, Ted Zlatanov <t...@lifelogs.com> wrote:
> On Tue, 12 Aug 2008 00:37:52 -0700 (PDT) Xah <xah...@gmail.com> wrote:
>
> > Ted Zlatanov wrote:
> > > The usability metrics (fairly standard in the industry) are listed in
> > >http://www.catb.org/~esr/writings/taouu/taouu.html#id2998837soplease
> > > see their definitions.
>
> > > - concise
> > > - expressive
> > > - easy (in the sense of "mnemonic load")
> > > - transparent
> > > - scriptable
> > > - discoverable
>
> X> That's from “The Art of Unix Usability” by Eric S Raymond.
>
> X> These cult-like books are rather snake oil.
>
> I disagree that this particular book is in any way cult-like, but that's
> irrelevant. What's important is the list of usability metrics as it
> applies to Emacs; if you disagree with that list then provide a better
> one.
A better book on issues such as software intereface and usability, in
my opinion, are for example:
• The Unix-Hater's handbook, by Simson Garfinkel, Daniel Weise, Steven
Strassmann, and Don Hopkins. 1994. The entire book is available at
http://web.mit.edu/~simsong/www/ugh.pdf and local mirror: ugh.pdf.zip
• The Rise of “Worse is Better”↗ by Richard P Gabriel, 1991 (local
copy)
• “Java: Slow, ugly and irrelevant”, By Simson Garfinkel, 2001-01-08.
http://archive.salon.com/tech/col/garf/2001/01/08/bad_java/print.html,
(local copy)
• Joseph M. Newcomer. Optimization: Your Worst Enemy, 1999.
http://flounder.com/optimization.htm (local copy)
• Theodore W Gray, author of Mathematica frontend, on educational math
software, video games, and violence, 2002-05. http://www.theodoregray.com/BrainRot/index.html;
(local copy)
• the famous “Go To Statement Considered Harmful” by computer
scientist Edsger W Dijkstra, 1968. http://www.acm.org/classics/oct95/;
(local copy)
• Steve Job's interview by Wired (1996-02), on education system and
design. Steve Job is a insightful man. http://www.wired.com/wired/archive/4.02/jobs_pr.html.
(Local copy)
• Suck.com's Greg Knauss on Netscape and the “Skin” phenomenon.
http://www.suck.com/daily/2000/04/10/daily.html; (Local copy)
• Communications of the ACM 34, 4 (April 1991), 18. Henry G Baker,
1990. (On the harm of speed) http://home.pipeline.com/~hbaker1/letters/CACM-DubiousAchievement.html;
(local copy)
• Jamie Zawinski, notorious programer of xemacs and Netscape web
browser, has written a webpage that contains codes from Netscape
browser before its OpenSource release. Note the profanity laiden
comments and what they say. It gives a indication of the pain and
fucked-up-ness of computing industry. http://www.jwz.org/doc/censorzilla.html
(2004-08-02 local copy)
• Let's Make Unix Not Suck↗, by Miguel De Icaza, 1999.
• Code Complete : A Practical Handbook of Software Construction by
Steve C McConnell (amazon.com↗). Throw away all your Design Patterns
or eXtreme Programming books. If you want a scientific book on
software development analysis, read this book instead.
• Alan Cooper, The Inmates Are Running the Asylum: Why High Tech
Products Drive Us Crazy and How To Restore The Sanity. 1999.
(amazon.com↗) This book explains away the errors of today's softwares.
Alan Cooper also wrote the book About Face, on software interface
design.
These are excerpts from:
http://xahlee.org/UnixResource_dir/paradigm.html
---------------------
Above are compiled around 2002 so is slightly outdated, and is more
geared towards software engineering and unix industry issues.
However, as a example of real software interface books, i'd recommend
Apple Human Interface design, and similar publication by Microsoft.,
and the references, researches, cited in these books.
A more practically accessable resource, is here:
http://en.wikipedia.org/wiki/User_interface_design
from there, one can find tens more articles and references, that are
more quality references then any of those from the mouths of crackpots
the likes of Larry Wall or Eric Raymond. (disclaimer: all mention of
real persons are opinion only)
Xah
∑ http://xahlee.org/
☄
next prev parent reply other threads:[~2008-08-12 14:48 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-05 16:44 Can anybody tell me how to send HTML-format mail in gnus M.T
2008-08-06 19:17 ` Evans Winner
2008-08-06 20:37 ` M.T
2008-08-07 5:09 ` Tim X
2008-08-07 14:34 ` Xah
2008-08-07 15:17 ` Cor Gest
2008-08-07 16:50 ` Xah
2008-08-07 17:14 ` M.T
2008-08-07 18:32 ` Xah
2008-08-07 18:07 ` Evans Winner
2008-08-08 12:20 ` Xah
2008-08-08 15:15 ` Ted Zlatanov
2008-08-08 15:39 ` Xah
2008-08-08 19:00 ` Ted Zlatanov
2008-08-09 19:18 ` Xah
2008-08-11 14:52 ` Ted Zlatanov
2008-08-11 15:49 ` Lennart Borgman (gmail)
2008-08-11 19:09 ` Eli Zaretskii
2008-08-11 19:27 ` Alan Mackenzie
2008-08-11 19:50 ` Eli Zaretskii
2008-08-11 19:31 ` Lennart Borgman (gmail)
2008-08-11 19:52 ` Eli Zaretskii
2008-08-11 20:14 ` Lennart Borgman (gmail)
2008-08-12 19:12 ` Eli Zaretskii
2008-08-12 19:22 ` Lennart Borgman (gmail)
2008-08-12 19:27 ` Alan Mackenzie
2008-08-11 20:20 ` Nikolaj Schumacher
[not found] ` <mailman.16396.1218482758.18990.help-gnu-emacs@gnu.org>
2008-08-11 20:57 ` Emacs usability (was: Can anybody tell me how to send HTML-format mail in gnus) Ted Zlatanov
2008-08-11 22:14 ` Emacs usability Lennart Borgman (gmail)
2008-08-12 7:37 ` Emacs usability (was: Can anybody tell me how to send HTML-format mail in gnus) Xah
2008-08-12 14:14 ` Emacs usability Ted Zlatanov
2008-08-12 14:48 ` Xah [this message]
2008-08-12 14:55 ` Emacs usability (was: Can anybody tell me how to send HTML-format mail in gnus) Xah
2008-08-12 18:29 ` Eli Zaretskii
[not found] ` <mailman.16413.1218492872.18990.help-gnu-emacs@gnu.org>
2008-08-12 14:17 ` Emacs usability Ted Zlatanov
2008-08-11 16:03 ` Can anybody tell me how to send HTML-format mail in gnus Xah
[not found] ` <mailman.16376.1218469770.18990.help-gnu-emacs@gnu.org>
2008-08-11 16:32 ` Ted Zlatanov
2008-08-11 16:52 ` Lennart Borgman (gmail)
2008-08-08 15:42 ` Cor Gest
2008-08-07 18:12 ` Cor Gest
2008-08-08 4:59 ` Sivaram Neelakantan
2008-08-08 5:54 ` Tim X
2008-08-08 13:11 ` Xah
2008-08-08 14:56 ` Phil Carmody
2008-08-08 15:42 ` Xah
2008-08-08 17:06 ` Phil Carmody
2008-08-08 17:22 ` Xah
2008-08-08 18:24 ` Cor Gest
2008-08-09 19:41 ` Xah
2008-08-09 21:03 ` Cor Gest
2008-08-09 22:23 ` Xah
2008-08-11 5:03 ` Charles philip Chan
[not found] ` <mailman.16348.1218431146.18990.help-gnu-emacs@gnu.org>
2008-08-11 5:44 ` Xah
2008-08-11 7:30 ` Charles philip Chan
[not found] ` <mailman.16351.1218439913.18990.help-gnu-emacs@gnu.org>
2008-08-11 8:16 ` Xah
2008-08-08 22:15 ` Phil Carmody
2008-08-09 10:16 ` Xah
2008-08-09 13:19 ` Sean Sieger
[not found] ` <mailman.16182.1218288014.18990.help-gnu-emacs@gnu.org>
2008-08-09 14:19 ` Xah
2008-08-10 9:52 ` Phil Carmody
2008-08-10 17:28 ` Xah
2008-08-08 15:19 ` Tim X
2008-08-08 17:14 ` Xah
2008-08-09 9:55 ` Tim X
[not found] ` <mailman.16065.1218171579.18990.help-gnu-emacs@gnu.org>
2008-08-08 12:35 ` Xah
2008-08-09 5:54 ` qingant
2008-08-09 8:13 ` Phil Carmody
2008-08-09 14:34 ` Alan Mackenzie
2008-08-06 22:21 ` Jashy
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d476bf22-aa9e-45e0-a13d-0f5a9c29e2e3@r35g2000prm.googlegroups.com \
--to=xahlee@gmail.com \
--cc=help-gnu-emacs@gnu.org \
/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).