From: Adam Thornton <athornton@gmail.com>
To: David Arnold <davida@pobox.com>
Cc: Computer Old Farts Followers <coff@tuhs.org>
Subject: Re: [COFF] Scribe (Typesetting System) and Unix
Date: Thu, 13 Jan 2022 18:53:14 -0700 [thread overview]
Message-ID: <CAP2nic0h-pY3AEiWF-7=W45ig_QbLRC5MKjq0QHz7p8gD3fArg@mail.gmail.com> (raw)
In-Reply-To: <1A1EC0A2-4E57-4810-8765-570D1A5E2C16@pobox.com>
[-- Attachment #1.1: Type: text/plain, Size: 927 bytes --]
On Thu, Jan 13, 2022 at 4:00 PM David Arnold <davida@pobox.com> wrote:
>
> Ironically, around that same time, Word for Windows 2.0 was IMHO the peak
> of that product’s functionality, in that while it allowed the user to
> randomly apply styling to the text, it was the last version that made the
> template facilities an equal first-class citizen in the UI. It was almost
> as easy to define and use “semantic” styles for formatting as it was to
> just do inline markup. Version 6 (they went from 2 to 6 in one hop) bent
> the product firmly towards use by amateurs, with toolbar buttons for
> bulleted lists, etc, that hid the underlying use of styles, and thus
> avoided users incrementally learning how to do consistent documents. From
> my perspective, every release since has made it worse.
>
>
Thank you for saying this. I agree and I thought I was the only person who
felt that way.
Adam
[-- Attachment #1.2: Type: text/html, Size: 1306 bytes --]
[-- Attachment #2: Type: text/plain, Size: 141 bytes --]
_______________________________________________
COFF mailing list
COFF@minnie.tuhs.org
https://minnie.tuhs.org/cgi-bin/mailman/listinfo/coff
next prev parent reply other threads:[~2022-01-14 1:53 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 2:04 josh
2022-01-13 2:03 ` Greg 'groggy' Lehey
2022-01-13 3:24 ` Win Treese
2022-01-13 14:56 ` Clem Cole
2022-01-13 15:08 ` John P. Linderman
2022-01-13 16:06 ` Clem Cole
2022-01-13 16:24 ` Warner Losh
2022-01-13 16:39 ` Harald Arnesen
2022-01-13 18:00 ` Bakul Shah
2022-01-13 15:35 ` Dan Cross
2022-01-13 16:02 ` Warner Losh
2022-01-13 16:20 ` Clem Cole
2022-01-13 16:32 ` Warner Losh
2022-01-13 16:42 ` Lars Brinkhoff
2022-01-13 16:52 ` Larry McVoy
2022-01-13 16:54 ` Clem Cole
2022-01-13 17:06 ` Clem Cole
2022-01-13 18:16 ` Dan Cross
2022-01-13 20:00 ` Larry McVoy
2022-01-13 20:26 ` Chet Ramey
2022-01-13 16:13 ` Charles H Sauer
2022-01-13 22:53 ` David Arnold
2022-01-14 1:53 ` Adam Thornton [this message]
2022-01-13 3:26 ` Theodore Ts'o
2022-01-13 16:25 ` Larry McVoy
2022-01-13 16:33 ` Dan Cross
2022-01-13 22:19 ` David Arnold
2022-01-13 13:54 ` Adam Sampson
2022-01-13 16:37 ` Lars Brinkhoff
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='CAP2nic0h-pY3AEiWF-7=W45ig_QbLRC5MKjq0QHz7p8gD3fArg@mail.gmail.com' \
--to=athornton@gmail.com \
--cc=coff@tuhs.org \
--cc=davida@pobox.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).