From: Adam Thornton <athornton@gmail.com>
To: "Lyndon Nerenberg (VE7TFX/VE6BBM)" <lyndon@orthanc.ca>
Cc: Computer Old Farts Followers <coff@tuhs.org>
Subject: Re: [COFF] [TUHS] Demise of TeX and groff (was: roff(7))
Date: Mon, 10 Jan 2022 20:22:49 -0700 [thread overview]
Message-ID: <8BCC2106-67EA-40D7-9C32-523FD7D7A3C1@gmail.com> (raw)
In-Reply-To: <4409b91cd794867d@orthanc.ca>
Taking this to COFF...
> On Jan 10, 2022, at 7:13 PM, Lyndon Nerenberg (VE7TFX/VE6BBM) <lyndon@orthanc.ca> wrote:
>
> Greg 'groggy' Lehey writes:
>
>> As long as man pages are formatted with ?roff, I don't see it going
>> away. I don't suppose many people use troff any more, but there are
>> enough of us, and as long as man pages stay the way they are, I don't
>> think we're in any danger.
>
> Well there is mandoc(1). But as time goes by they just seem to be
> re-implementing nroff. Of course that *must* be easier than just
> learning n/troff in the first place :-P
As someone who did a lot of a Ph.D. in the history of computing, and then went into IT because he liked eating protein sometimes:
The great secret is that NO ONE EVER READS THE LITERATURE.
We have now made all the mistakes at least four times:
Once for each of mainframes, minis, micros, and mobile.
You can be a rock star at any development or operations job, even if you are, like me, a Bear Of Little Brain, simply by having some idea of what was tried already to solve a problem like this, and why it didn't work.
Which you can get by actually stopping to read up about your problem before diving headfirst into coding up a solution for it.
If you happen to get stinking rich from this advice, you can buy me a bottle of whiskey sometime.
Adam
_______________________________________________
COFF mailing list
COFF@minnie.tuhs.org
https://minnie.tuhs.org/cgi-bin/mailman/listinfo/coff
parent reply other threads:[~2022-01-11 3:22 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <4409b91cd794867d@orthanc.ca>]
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=8BCC2106-67EA-40D7-9C32-523FD7D7A3C1@gmail.com \
--to=athornton@gmail.com \
--cc=coff@tuhs.org \
--cc=lyndon@orthanc.ca \
/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).