I Use Typst Now
Postedabout 2 months agoActiveabout 2 months ago
christopherbiscardi.comTechstory
calmpositive
Debate
20/100
TypstLatexMarkup LanguagesDocument Processing
Key topics
Typst
Latex
Markup Languages
Document Processing
The author has switched to using Typst, a markup language, and discusses its potential benefits and limitations, with commenters sharing their experiences and concerns about using Typst in their workflows.
Snapshot generated from the HN discussion
Discussion Activity
Light discussionFirst comment
5h
Peak period
2
36-39h
Avg / period
1.3
Key moments
- 01Story posted
Nov 6, 2025 at 7:51 PM EST
about 2 months ago
Step 01 - 02First comment
Nov 7, 2025 at 12:37 AM EST
5h after posting
Step 02 - 03Peak activity
2 comments in 36-39h
Hottest window of the conversation
Step 03 - 04Latest activity
Nov 8, 2025 at 9:31 AM EST
about 2 months ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
ID: 45842448Type: storyLast synced: 11/20/2025, 1:26:54 PM
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.
Instead I only use it as a markup language and use the typst libraries to evaluate it into blocks/AST which I then use together with askama templates.
This gives me a lot more flexibility, and typst is nicely extensible with custom typesafe functions. The downside is that existing LSP integrations don't recognize my custom keywords and show errors, something I just accept for now but might work around by importing a lib.ty stub (without real implementation, just matching signatures).
This is actually very little work to set up, have a look at: https://github.com/Relacibo/typst-as-lib (not my code, just something I found helpful)
It's a different set, not subset. I don't support some math and layout things that don't make sense on a webblog (or which I don't need). But I have custom elements for margin notes and such which typst doesn't have out of the box.
I don't like markdown - it's underspecified, typos turn into broken docs instead of compilation error and extending it is hard. I looked at rST which is close to what I want and what I would have used if I didn't find Typst, I just prefer the latter's syntax and also it's a rust library I can more easily work with.
Edit: also I'm not saying this is better or anything, it's just fun for me to build.
For now, it's an unhappy marriage of pandoc, LaTeX, and a 20k LOC Lua ecosystem for me.