The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Phil Budne <phil@ultimate.com>
To: tuhs@tuhs.org
Subject: [TUHS] Re: Documentation (was On Bloat and the Idea of Small Specialized Tools)
Date: Mon, 20 May 2024 15:27:24 -0400	[thread overview]
Message-ID: <202405201927.44KJROeX064950@ultimate.com> (raw)
In-Reply-To: <26187.39054.137077.761468@dobie-old.ylee.org>

Yeechang Lee:
> My understanding is that an unexpected result of the requirement to
> draft all federal laws in Canada in both English and French is
> something similar: The discussion process ensuring that a bill's
> meaning is identical in both languages helps rid the text of
> ambiguities and errors regardless of language.

It always seemed to me that ISO standards were written to be equally
incomprehensible in all languages, substituting terms like Protocol
Data Unit (PDU) for familiar ones like Packet.

In the early Internet, where there wasn't ANY money to be made in
antisocial conduct, it was easier to justify sentiments like "Rough
consensus and working code" and "be liberal in what you accept".

Lest ye forget, "industry standards" were once limited to things like
magnetic patterns on half-inch tape and the serial transmission of
bits, and at the LOWEST of levels.  Reading a tape written on another
vendor's system wasn't easy when I got started in the early 80's; In
addition to ASCII and EBCDIC, there were still systems with
vendor-specific 6-bit character sets, never mind punched cards.  I
remember going on a campus tour in the late 70's where there was an
ASCII terminal hooked up to some system that had BASIC (the standard
at the time was ANSI "Minimal BASIC"; a full(er) standard took long
enough that it was dead on arrival), but instead of "RETURN" required
typing CTRL/C (defined in ASCII as End Of Text) to enter a line!

In that context, getting ANYTHING working across vendors was a
victory, and having one system refuse to speak to another because of
some small detail in what one of them considered reasonable (or not)
was asking for trouble.

The times and stakes today are distinctly different.

      reply	other threads:[~2024-05-20 19:27 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-18 18:07 [TUHS] Re: On Bloat and the Idea of Small Specialized Tools Douglas McIlroy
2024-05-18 18:13 ` Brantley Coile
2024-05-18 18:18 ` Larry McVoy
2024-05-18 18:52   ` Clem Cole
2024-05-18 19:19     ` Luther Johnson
2024-05-18 20:12       ` segaloco via TUHS
2024-05-18 19:32     ` Stuff Received
2024-05-18 18:22 ` Ralph Corderoy
2024-05-19  8:58   ` [TUHS] The 'usage: ...' message. (Was: On Bloat...) Ralph Corderoy
2024-05-18 18:31 ` [TUHS] Re: On Bloat and the Idea of Small Specialized Tools Peter Weinberger (温博格) via TUHS
2024-05-18 20:33 ` Steffen Nurpmeso
2024-05-19  8:39   ` Marc Rochkind
2024-05-20  6:07     ` Adam Thornton
2024-05-20 15:43       ` [TUHS] Documentation (was On Bloat and the Idea of Small Specialized Tools) Paul Winalski
2024-05-20 16:37         ` [TUHS] " Andrew Hume
2024-05-20 18:38         ` Yeechang Lee
2024-05-20 19:27           ` Phil Budne [this message]

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=202405201927.44KJROeX064950@ultimate.com \
    --to=phil@ultimate.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).