The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: tfb@tfeb.org (Tim Bradshaw)
Subject: [TUHS] attachments: MIME and uuencode
Date: Sun, 12 Mar 2017 13:53:55 +0000	[thread overview]
Message-ID: <546F4B1E-5995-43BD-BC36-3CD26EED455C@tfeb.org> (raw)
In-Reply-To: <71748884-ac1a-d565-aa08-80f9220594ac@mhorton.net>

> On 11 Mar 2017, at 19:07, Mary Ann Horton <mah at mhorton.net> wrote:
> 
> When MIME came out in 1992 I became a champion of SMTP/MIME as a standard - it was a big improvement.  But uuencod predated MIME by 12 years.

Somewhere I may have a copy of a rant I wrote in about 1995 called 'MIME as a disease vector'.   It argued that the single biggest thing that MIME did was to establish the Windows/Office monopoly, and that this was why MS were so enthusiastic about it.  It did this by making it trivial for a Windows user to send documents in Office formats which, if you wanted to read or modify them, required you to use Windows.  Thus the disease (proprietary formats and monopolies) was effectively spread by MIME.

I still think it's essentially correct, although I would not now use such loaded wording, and also clearly this was just inevitable: MIME or some equivalent way of sending typed binary data by email was useful, and this undesirable consequence unavoidable.  Looking at things from the other side of the Windows monopoly period it all looks less horrible as well: Windows didn't end up killing Unix even.

--tm


  parent reply	other threads:[~2017-03-12 13:53 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-11 19:07 Mary Ann Horton
2017-03-11 23:01 ` Paul Winalski
2017-03-11 23:05   ` Mary Ann Horton
2017-03-12  1:14     ` Dan Cross
2017-03-12  6:28       ` jsteve
2017-03-12 23:41         ` Gregg Levine
2017-03-13  0:00           ` Larry McVoy
2017-03-13  1:59             ` Dave Horsfall
2017-03-12 23:43       ` Mary Ann Horton
2017-03-12 21:10   ` Dave Horsfall
     [not found]     ` <12de3888-3a82-4a8c-9177-50e6cb4cb931.maildroid@localhost>
2017-03-19  2:34       ` Dave Horsfall
2017-03-12 13:53 ` Tim Bradshaw [this message]
2017-03-12 17:42 ` Clem Cole
2017-03-12 23:35   ` Mary Ann Horton
2017-03-13  0:07     ` Clem Cole
2017-03-13  0:09     ` Warren Toomey
2017-03-13  0:11       ` Clem Cole
2017-03-12 15:10 Noel Chiappa
2017-03-12 18:13 Doug McIlroy
2017-03-12 18:22 ` Larry McVoy
2017-03-12 18:26 ` Clem Cole
2017-03-13  0:34   ` Dan Cross
2017-03-13  1:28     ` Larry McVoy
2017-03-13  5:39       ` Dave Horsfall
2017-03-13 11:37   ` Steffen Nurpmeso
2017-03-13 20:21     ` Steffen Nurpmeso
2017-03-13 22:14       ` Doug McIlroy
2017-03-14 10:49         ` Steffen Nurpmeso
2017-03-12 18:33 ` Paul Winalski
2017-03-13  5:58   ` Dave Horsfall
2017-03-12 18:57 Andy Valencia
2017-03-12 20:04 Noel Chiappa
2017-03-12 21:34 ` Random832
2017-03-12 22:12   ` Noel Chiappa
2017-03-13 14:58     ` Michael Kjörling
2017-03-13 21:56       ` Dave Horsfall
2017-03-14 10:33         ` Steffen Nurpmeso
2017-03-16 18:52         ` Michael Kjörling

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=546F4B1E-5995-43BD-BC36-3CD26EED455C@tfeb.org \
    --to=tfb@tfeb.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).