Computer Old Farts Forum
 help / color / mirror / Atom feed
From: crossd at gmail.com (Dan Cross)
Subject: [COFF] [TUHS] Looking for final C compiler by Dennis Ritchie
Date: Mon, 23 Jul 2018 12:41:46 -0400	[thread overview]
Message-ID: <CAEoi9W7C=JtmPMuYQVUdWmbDbCzLL1w-D0Xtuguf64Ow-CV9dQ@mail.gmail.com> (raw)
In-Reply-To: <20180723155552.GB19635@mcvoy.com>

[+COFF and TUHS to Bcc:]

Okay, here we go: troff vs. TeX food fight.

On Mon, Jul 23, 2018 at 11:56 AM Larry McVoy <lm at mcvoy.com> wrote:

> I actually wacked a bunch of the Unix docs to make them look a little
> better, I should see if I can find that.
>

I'd like to see that; presentation of some of those docs is getting a bit
long in the tooth.

I agree that roff is awesome, it's a bummer that Latex seems to be
> the winner (which I think is purely because the roff/eqn/pic/etc
> docs weren't widely available back in the day).
>

I have to disagree with this, however. TeX (and more specifically LaTeX)
won out for technical writing because, frankly, it produces nicer output
than *roff did. If I were writing a thesis or paper, I'd frankly rather use
LaTeX or AMSLaTeX.

I've used eqn to try and typeset math; it's OK if it's all that you've got.
An nroff approximation for output to the terminal is kind of nifty, but
beyond that it simply pales in comparison to TeX. I know that people have,
and perhaps still do, typeset mathematics with eqn/neqn/troff, but given a
choice between the two, I think you'd be hard pressed to find a
mathematician who would choose troff over TeX; similarly with most
technical papers.

Now tbl and pic, those are pretty cool. Even then, GNU pic will output TeX
for incorporation into other documents, and LaTeX has some very nice
table-creation environments that largely subsume the functionality of tbl.

Now don't get me wrong, I *like* roff, and I use it occasionally for
one-off things, but for serious writing for publication I'd generally chose
LaTeX.

        - Dan C.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20180723/f9f72ab3/attachment.html>


       reply	other threads:[~2018-07-23 16:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8ECDA62D-1B54-4391-A226-D3E9ABEE4C07@planet.nl>
     [not found] ` <CACXZuxeJ3igMtfbLs1iUPMLhomQUG0dEjpaHHmV0L7hF0bvo4g@mail.gmail.com>
     [not found]   ` <CAC20D2OTsR0ZxqeUk2EBpZnWy2k4LVf8=VPKzitWhkT3n_vL8g@mail.gmail.com>
     [not found]     ` <20180723155552.GB19635@mcvoy.com>
2018-07-23 16:41       ` crossd [this message]
2018-07-24  3:52         ` [COFF] roff vs. Tex (was: Looking for final C compiler by Dennis Ritchie) grog
2018-07-24  4:01           ` lm
2018-07-24 14:43             ` cym224
2018-07-24 10:00           ` ralph
2018-07-27  1:04             ` lm
2018-07-25 21:24           ` perry
2018-07-26  4:22             ` grog
2018-07-26  6:38               ` bakul
2018-07-26 12:22               ` perry
2018-07-27  1:28                 ` grog
2018-07-27  2:52                   ` cym224

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='CAEoi9W7C=JtmPMuYQVUdWmbDbCzLL1w-D0Xtuguf64Ow-CV9dQ@mail.gmail.com' \
    --to=coff@minnie.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).