Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I think Typst looks really interesting for some scenarios, but inadequate for others.

I like RST a lot for Python documentation, because of all the directives for types, admonitions, and lots of domain-specific stuff. I wouldn't use RST if I'm writing a book, or a research paper.

In the same way, Typst looks like a great candidate for those last examples, but is likely unsuitable for documenting a library written in Python.





> In the same way, Typst looks like a great candidate for those last examples, but is likely unsuitable for documenting a library written in Python.

why though?

Would you categorize Markdown as unsuitable as well? if so, why?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: