Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@extundo.com>
Cc: Ken Raeburn <raeburn@raeburn.org>, <ding@gnus.org>
Subject: Re: "CNET imagines the perfect e-mail client" - can Emacs be it?
Date: Mon, 8 Apr 2002 14:09:38 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.44.0204081350280.24182-100000@yxa.extundo.com> (raw)
In-Reply-To: <rj6632qwwh.fsf@zuse.dina.kvl.dk>

On Mon, 8 Apr 2002, Per Abrahamsen wrote:

> Ken Raeburn <raeburn@raeburn.org> writes:
> 
> > http://home.cnet.com/software/0-8888-8-9161160-1.html
> 
> I did read it.  I do not think that what they want would make sense to
> implement in Emacs, they are clearly targetting a completely different
> market. 

I didn't read it, but in theory I don't see a conflict between eye candy
and user friendlyness and the amount of customizations possible in Gnus.  
In essence, I don't see why Gnus can't fit everyone.  Emacsen seem to have
GTK soon, and then Gnus could use all those colors and bitmaps and
multimedia wizards and transperancy and themes and ripple effects and
sound effects that everyone absolutely needs.

The problem with user friendlyness in applications generally is that they 
are implemented poorly.  Gnus can do better.  It can be user friendly AND 
expert friendly.

In practice there is the problem of finding someone who wants to implement
though..




  reply	other threads:[~2002-04-08 12:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-06 22:26 Ken Raeburn
2002-04-07  0:42 ` Sean Neakums
2002-04-07  0:48   ` Sean Neakums
2002-04-08 10:58 ` Per Abrahamsen
2002-04-08 12:09   ` Simon Josefsson [this message]
2002-04-08 15:28   ` Wes Hardaker
2002-04-08 16:54     ` Per Abrahamsen
2002-04-08 17:54   ` Ken Raeburn
2002-04-08 22:51     ` news
2002-04-09 17:40       ` Kai Großjohann
2002-04-10 15:19         ` news
2002-04-10 17:32           ` Kai Großjohann

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.LNX.4.44.0204081350280.24182-100000@yxa.extundo.com \
    --to=jas@extundo.com \
    --cc=ding@gnus.org \
    --cc=raeburn@raeburn.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 NNTP newsgroup(s).