@shaknais

Yes, Donald Knuth is a hero and a true renaissance man, and his TeX is an unsurpased achievement, a tool of lasting value.

Back in 1996 I took a few months off for an in-depth study of Knuth's TeX: tokens and boxes and output routines and all. I used plain TeX to write a flexible little macro package for myself, with a minimalist input syntax, set up for my own writing, tailored to my own writing needs.

I still use that same package today, 30 years later, unchanged except for project-specific adjustments. All the materials I give to my students are written in that package, all my papers. A stable writing framework for a lifetime. Few other systems have such stability and power. Thank you, Donald Knuth.

#DonaldKnuth #plainTeX #WritingTools

@pait I think it depends on how much faster it would become, and honestly I am not sure how much faster it could be made. The thing is that computers are significantly more parallel and have a much larger memory bandwidth nowadays...

One reason for considering optimising is that packages are becoming significantly more complicated. (The same increase in complexity happens in software -- e.g., it's not anymore possible for a small team to write a new operating system from scratch.) Two things that are somewhat painful are making slides with beamer and running latexmk in the background. Another use case is for people in overleaf, for example (in part because the two-pane text|preview editor creates an expectation of fast preview cycles).

But already there is about an order of magnitude difference in speed from #plainTeX to #LaTeX. Of course, the latter is doing significantly more work than the former, but still.

@ireneista

Not sure it counts, but I couldn't cope with the braces-heavy syntax of #LaTeX and wrote my own macro package in #PlainTeX. Have done books in it, all my lecture notes etc. Main design and core commands unchanged since 1997!

Syntax uses empty space and empty lines as delimiters. Eg, my source says

"\ch Introduction

In this book ..."

and TeX then typesets this as chapter 1 with title "Introduction" and "In this book ..." as first para.]

@mpjgregoire

Guilty as charged! :-) In my defense, setting up my own macros gave me control over the markup syntax. When writing, I want to use "natural markup", simple commands inserted naturally into the text. Eg, for a new chapter I write

"\chap The Framework

In this chapter, we will ..."

And if I want to \emw emphasise a single word, I simply insert the \emw command before the word. Empty spaces or empty lines act as natural delimiters.

No \begin{}\end{} straightjacket!

#PlainTeX

@mpjgregoire

Indeed. And the best thing about working in #PlainTeX is the sense of accomplishment you get when completing a standard task with your own macros --- and to do so almost as well as your buddies do with out-of-the-box #LaTeX commands. :-)

#AndWhyNot

Donald E. Knuth は書き始める前から文書の章構成を完璧に思い描けるから,後から章番号を付け直すということもなくて,したがって plain TeX の見出し命令には自動ナンバリングの仕組みがない #plainTeX

増刷する度に新しい組版環境をキャッチアップするのが嫌な人におすすめの構成:

Knuthian TeX + plainTeX

#TeX #plainTeX #アレ

(plain) TeX のアライメント(表組み)が思ったより難しくて泣いてる……こういうときに LaTeX の偉大さが改めて感じられるな #TeX #plainTeX #LaTeX