• I want to use it, but if I’m going to commit to learning a new system for my work, I need to know that 1) it will remain open source (like LaTeX), 2) its going to remain maintained, 3) it has a robust package library, 4) it has to understand bibtex. I dont think typst has committed to the first, its not mature enough for 2 or 3, and I cannot for the life of me figure out how to automate translation between bibtex and their funky format.

  • Without having tried typst myself, I would still recommend learning LaTeX, if you’re ever looking to publish in a scientific journal; most journals accept submissions in either Word (which in my mind is a very painful tool to use, especially when it comes to typesetting and equations) or LaTeX. They then typically convert the input to some internal format, but are probably unlikely to add support for new formats.

    If you only ever intend to write documents for your own purposes, use whichever format you like the best; I personally use Emacs Org-mode and LaTeX export.

  • To me the syntax feels very strange but I adapt to a lot of things. Does anyone have experience with it and already a more profound opinion?

    Markdown is already a very easy interface to latex and html. And latex has been there since forever.

  • I’ve been really happy with it; I’ve been using it for templating reports at work for months now. I’ve just started experimenting with using jinja to pretemplate my template lol.

    I’ll probably continue down that track to try and automate my workflow away so I can focus on less tedious things, but after you get used to the box encapsulation it becomes fairly easy to work with!