Hacker News Reader

Always pleased to see Typst mentioned. TeX made a lot of choices that made sense at the time, but TeX macros and C #defines especially when nested and/or not properly bracketed to allow nesting are a mess when things go wrong.

View on HN

It is fun how in computer science terms, TeX and Typst are so incredibly far apart. TeX is a macro language that could be implemented in very little memory, while Typst literally memoizes every typst function's result; to the point where it will eat all available memory if the document and its editing increments needs it.

This reflects the time in which they were developed.

In what setting are you mixing LaTeX and C code?

No, no, TeX macros nested within other TeX macros.

Pretty common to emit latex from C, no?

Reply on news.ycombinator.com