The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: arnold@skeeve.com
To: tuhs@minnie.tuhs.org, nobozo@gmail.com
Subject: Re: [TUHS] eqn
Date: Sun, 06 Oct 2019 02:03:26 -0600	[thread overview]
Message-ID: <201910060803.x9683QTm020295@freefriends.org> (raw)
In-Reply-To: <389f5a69-e103-7ec3-9b95-3e6e294a86e6@gmail.com>

Jon Forrest <nobozo@gmail.com> wrote:

> One slightly OT fact about TeX. On my 16GB, Core i7, SATA SSD
> Lenovo T430s laptop running Fedora 30, it takes ~3 seconds to run TeX on
> the ~900 page TeXBook. That's pretty fast.

You can thank Moore's Law for this. I remember trying to run TeX on
BSD 4.[12] vax with 4 Meg of memory and it taking many minutes to format
a single page.

The first time it became easy to run TeX, for me, was on sparcstation
class systems in the early 1990s.

> TeX contains all kinds of
> code to make it fit in the constraints of a 1980s computer. I wonder
> whether a redesign for a 2020 computer would be faster or slower.

I think it's just compute-intensive code. Moern versions of TeX use
WebToC to translate Knuth's web/pascal code to C, and that has been
the case for a long time.

(As an aside, everyone here who's read "TeX: The Program", raise
you hand.  [I have, but only once.])

> I suspect, but can't prove, that classic [nt]roff might also
> benefit in the same way. groff was written latter, so it might
> suffer less.

I don't think classic [nt]roff suffers at all. I remember (boy do I sound
like an old f*art) circa 1991, having both nroff and groff on a '486 class
system.  nroff was noticeably faster at formatting man pages than
groff was.  (Groff, of course, was ditroff and gave me PostScript output,
but comparing the two versions of nroff for text output, there
was a noticeable difference.)

Again, today, it doesn't really matter.

Arnold

  parent reply	other threads:[~2019-10-06  8:04 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-04  4:20 Larry McVoy
2019-10-04  4:35 ` Dave Horsfall
2019-10-04  5:12 ` George Michaelson
2019-10-04 13:43   ` Nemo
2019-10-04 14:57 ` aksr
2019-10-04 15:52   ` U'll Be King of the Stars
2019-10-04 16:12     ` Jon Forrest
2019-10-04 17:24       ` Adam Thornton
2019-10-04 18:55         ` Kurt H Maier
2019-10-04 17:43       ` Steffen Nurpmeso
2019-10-06  8:03       ` arnold [this message]
2019-10-04 19:02     ` Larry McVoy
2019-10-07 17:26     ` Seth J. Morabito
2019-10-07 19:14       ` Adam Thornton
2019-10-08 21:11         ` Seth Morabito
2019-10-04 19:25 ` Fabio Scotoni
2019-10-05  1:59 Doug McIlroy

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=201910060803.x9683QTm020295@freefriends.org \
    --to=arnold@skeeve.com \
    --cc=nobozo@gmail.com \
    --cc=tuhs@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).