The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Larry McVoy <lm@mcvoy.com>
To: Rob Pike <robpike@gmail.com>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: Bell Foreign-Language UNIX Efforts
Date: Tue, 21 Mar 2023 19:25:26 -0700	[thread overview]
Message-ID: <20230322022526.GI3779@mcvoy.com> (raw)
In-Reply-To: <CAKzdPgxYPS3-XAJh2bzBRxSeJPO4tyietcNY+eyUvfYGR8fHow@mail.gmail.com>

The brilliance of UTF-8 was to encode ASCII as is.  That seems obvious in
retrospect but as Rob says, the multibyte crud in C89 was just awful,
and that was the answer at the time.  Fitting ASCII in as is meant
that all of the Unix utilities, sed, grep, awk, etc, had close to no
performance hit if you were processing ascii.  That's pretty cool when
you get that and you can process Japanese et al as well.

I kind of cringe when I say it is brilliant to not break what exists
already, to me, that's just part of what you do as an engineer.  But
history has shown that not breaking stuff, fitting the new into the 
old, is brilliant.  So kudos to Rob and Ken for doing that (but truth
be told, I'd be stunned if they didn't, they are great engineers).

On Mon, Mar 20, 2023 at 07:27:34AM +1100, Rob Pike wrote:
> As my mail quoted in
> https://www.cl.cam.ac.uk/~mgk25/ucs/utf-8-history.txt says,
> Ken worked out a new packing that avoided all the problems with the
> existing ones. He didn't alter Prosser's encoding. UTF-8, as it was later
> called, was not based on anything but it was deeply informed by a couple of
> years of work coming to grips with the problem of programming with
> multibyte characters. What Prosser did do, and what we - all of us - are
> very grateful for, is start the conversation about replacing UTF with
> something practical.
> 
> (Speaking of design by committee, the multibyte stuff in C89 was atrocious,
> and I heard was done in committee to get someone, perhaps the Japanese, to
> sign off.)
> 
> Regarding windows, Nathan Myrhvold visited Bell Labs around this time, and
> we tried to talk to him about this, but he wasn't interested, claiming they
> had it all worked out. We later learned what he meant, and lamented. Not
> the only time someone wasn't open to hear an idea that might be worth
> hearing, but an educational one.
> 
> It's important historically to understand how all the forces came together
> that day. The world was ready for a solution to international text, the
> proposed character set was acceptable to most but the ASCII compatibility
> issues were unbearable, the proposed solution to that was noxious, various
> committees were starting to solve the problem in committee, leading to
> technical briefs of varying quality, none right, and somehow a phone call
> was made one afternoon to a couple of people who had been thinking and
> working these issues for ages, one of whom was a genius. And it all worked
> out, which is truly unusual.
> 
> -rob

-- 
---
Larry McVoy           Retired to fishing          http://www.mcvoy.com/lm/boat

  parent reply	other threads:[~2023-03-22  2:25 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-19  5:00 [TUHS] " segaloco via TUHS
2023-03-19 13:32 ` [TUHS] " Diomidis Spinellis
2023-03-19 13:47   ` [TUHS] " Ralph Corderoy
2023-03-19 20:27     ` [TUHS] " Rob Pike
2023-03-20  7:55       ` arnold
2023-03-20  9:22         ` Rob Pike
2023-03-20 11:02           ` arnold
2023-03-20 15:44         ` Steffen Nurpmeso
2023-03-20 22:01           ` John Cowan
2023-03-20 22:28             ` Steffen Nurpmeso
2023-03-22  2:25       ` Larry McVoy [this message]
2023-03-22  2:52         ` Rob Pike
2023-03-22  7:12           ` Mehdi Sadeghi via TUHS
2023-03-22  7:33             ` Rob Pike
2023-03-22  7:40               ` arnold
2023-03-22 10:02                 ` Skip Tavakkolian
2023-03-22 10:09                   ` Skip Tavakkolian
2023-03-22 12:02                     ` Rob Pike
2023-03-22 22:33                       ` Steffen Nurpmeso
2023-03-22 23:33                         ` segaloco via TUHS
2023-03-23  0:01                           ` Warren Toomey via TUHS
2023-03-19 13:38 ` Edouard Klein

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=20230322022526.GI3779@mcvoy.com \
    --to=lm@mcvoy.com \
    --cc=robpike@gmail.com \
    --cc=tuhs@tuhs.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).