jsm on Nostr: After some thought, all new projects will use Typst and I can just switch old ...

After some thought, all new projects will use Typst and I can just switch old projects to just use Typst as the pdf engine instead of LaTeX because the Typst compiler is stupidly fast. One small CLI flag change in a Makefile and compilation is now stupidly fast.

quoting nevent1q…k3ek

Considering moving from a hacked together setup of Pandoc Markdown, Makefiles, Python scripts, and a sprinkling of Jinja templates and raw Latex to Typst.

Does anyone have experience switching from Markdown to Typst? To me it seems like it optimizes well for making the hot path of the markup used for most documents look similar to Markdown while also allowing you to drop down into lower levels of abstraction seamlessly.

Any footguns or horror stories I should know before I put in the effort to switch?