Gnus development mailing list
 help / color / mirror / Atom feed
From: Karl Kleinpaste <karl@justresearch.com>
Subject: Re: metamail
Date: 08 Dec 1998 13:38:56 -0500	[thread overview]
Message-ID: <vxklnkibhrz.fsf@beaver.jprc.com> (raw)
In-Reply-To: François Pinard's message of "08 Dec 1998 12:17:15 -0500"

I'm well aware of where metamail originated, and in fact I
experimented with the very first public release he made of it (with
related tools) in ¿1992?.  It is still the case that it's quite ugly
in some ways, and is incomplete, as we've found when looking for MIME
comparison points against Gnus.

Borenstein published a fair amount of commentary about having spent N
years working with things like CMU's Andrew Message System (a
seriously spiffy and capable system which supported advanced concepts
like embedded animation, as far back as the mid-1980s; I recall
watching him demo this kind of thing at the January 1988 Usenix Conf.)
and yet, much later, found himself back-porting MIME-related hooks
into ancient crufty mail handlers like UCB Mail because, as he
related, composition of such messages is Hard -- that one can spend a
great deal of time putting together even a short message when one is
trying to get the right presentation of graphic, animation, and text,
and that there is a "diminishing returns" factor involved, which
limited the AMS' ability to achieve penetration and acceptance.

I consider the deficiencies of metamail in particular to be an example
of the realization that effective rendering is apparently equally as
Hard as composition.


  reply	other threads:[~1998-12-08 18:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-12-08 16:43 metamail Jake Colman
1998-12-08 16:47 ` metamail Karl Kleinpaste
1998-12-08 17:17   ` metamail François Pinard
1998-12-08 18:38     ` Karl Kleinpaste [this message]
1998-12-08 19:29   ` metamail Jake Colman
1998-12-09  9:36   ` metamail Steinar Bang
1998-12-09 11:49     ` metamail Kai.Grossjohann

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=vxklnkibhrz.fsf@beaver.jprc.com \
    --to=karl@justresearch.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 NNTP newsgroup(s).