The real problem is acceptance of non-word/latex papers
Some scientific journals, which only provides a Word template, require you to print to PDF to submit, then ships this PDF to India, where a team recreates the look of the submission in LaTeX, which is then used to compose the actual journal. I wish this was hyperbole. For these journals, you can safely create a LaTeX-template looking _almost_ the same, and get away with it.
So its a mass and momentum problem. Typst not only has to be better/easier/faster than latex, but to a degree that it justifies all of the labor and time to learn it and change all that existing template and utility infrastructure built up over decades. A high bar.
If Typst (or some other new contender) could also read and compile latex code and packages alongside its own syntax then that would be a game-changer. Then I can use all my old stuff and gradually change things over to typst (or whatever).
Typst is a breath of fresh air. Interacting with modern tooling (GitHub, discord). Responsive developers. Easy to read code. Easy to do things on your own.
Admittedly, my use case is mainly writing books, I've never published an academic paper.
My experience with word processing is that spending a lot more time on UI bugs and incosistencies using any wysiwyg editors, compare to those any markup based system (md, latex, typst) is significant improvement. Typst is just simply faster, cleaner alternative to LaTex. I hope it gets much more popular.
My main selling points is that with LaTeX, it is easy to create typography shines beauty for a distance. (Often way better that most of books you find in stores.) With other typesetting systems, usually it is not the case. Yet, I am waiting for new things that offer simplicity, yet have same (or better!) visuals that LaTeX.
Typst apparently uses Knuth-Plass, but I don't see any information about microtypography.
Things like default margins, in my opinion, are a lot easier to fix than these other issues.
I wrote a post half year ago explained the details for my decision between LaTeX and Typst: https://blog.ppresume.com/posts/on-typesetting-engines#typst
pros:
- one small compiler that can output: pdf, png, svg, html
- compilation is fast (see below)
- syntax is much cleaner than Latex
- few ways of to a thing
- already has all the templates most people need
- tooling is good enough with VS Code
- supports SVG images
cons:
- less users?