Typst: An easy to learn alternative for LaTex

Original Article ↗ Hacker News Discussion ↗

Overall sentiment

  • Many commenters find Typst significantly more pleasant, intuitive, and faster than LaTeX for most everyday and technical documents.
  • Others are cautious or skeptical, citing missing features, accessibility, and long‑term viability versus LaTeX.

Typst vs. Markdown

  • For simple prose and web content, several argue Markdown (plus CSS, static site generators, or pandoc) is sufficient and often preferable.
  • Typst is seen as useful when you need precise page layout, printing, PDFs, citations, table of contents, indexes, figure captions, or “document” rather than “web page” workflows.
  • Some demonstrate that Markdown→XML→TeX→PDF pipelines can also cleanly separate content from presentation, countering the idea that this separation requires Typst.

Typst vs. LaTeX

  • Typst is praised as easier to learn, more intuitive, and much faster to compile, with a real scripting language and JSON input instead of TeX macros.
  • It is already replacing LaTeX for resumes, technical reports, character sheets, certificates, invoices, and mass‑generated PDFs.
  • LaTeX is still preferred for: complex math, rich package ecosystem (tikz, amsmath, specialized tables), book production, tagged PDFs, and journal/arXiv workflows.
  • Some believe Typst can eventually match LaTeX’s capabilities; others think LaTeX’s decades‑old ecosystem and mandatory use in academia make it effectively irreplaceable.

Missing features & rough edges

  • Reported gaps: some fine typography in math (spacing classes, delimiter sizing ergonomics), bookmaking features (front matter, index, etc., status unclear), robust footnotes, footnotes in headings, automatic running headers in core, and advanced table formatting.
  • Packages and workarounds exist for several of these (headers, diagrams, slides), but commenters argue some should be built‑in.

HTML, accessibility, and formats

  • Typst is currently PDF‑focused; HTML export and better accessibility are in progress. Some refuse to adopt it until accessible output is solid.
  • There is debate over whether a modern LaTeX competitor should have prioritized HTML/ePub and accessibility from the start.
  • LaTeX’s newer HTML pipelines (lwarp, LaTeXML, arXiv converters) are cited as evidence that LaTeX is catching up on the web side.

Ecosystem, tooling, and longevity

  • Integrations mentioned: VS Code, Neovim live preview, Quarto, pandoc, PHP wrappers, JSON input, templates (letters, slides, headers).
  • Some worry about Typst’s commercial ties and long‑term maintenance, contrasting it with LaTeX’s perceived decades‑long stability, though others note LaTeX itself has maintenance and package‑compatibility issues.