# Typst and other alternatives to LaTeX

**URL:** https://discourse.julialang.org/t/typst-and-other-alternatives-to-latex/121652
**Category:** Offtopic
**Tags:** latex
**Created:** [October 22, 2024, 1:45am UTC](https://discourse.julialang.org/t/typst-and-other-alternatives-to-latex/121652 "2024-10-22T01:45:53Z")
**Posts on this page:** 1
**Showing post:** 98

<div class="post-metadata">

### Author: ![kapple](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/kapple/32/218915_2.png) [@kapple](https://discourse.julialang.org/u/kapple)
#### Post date: [November 2, 2024, 1:56am UTC](https://discourse.julialang.org/t/typst-and-other-alternatives-to-latex/121652/98 "2024-11-02T01:56:41Z")

</div>

In a comparison between Typst and LaTeX, another thing to consider is the development speed and quality.

We Julians like both the development speed _and_ performance speed when implementing projects in Julia. In 12+ years we’ve managed to rival and even surpass the performance and user experience of other ecosystems that have had 20+ years to hone their craft.

Typst has demonstrated that kind of progress as well, heck it’s already much faster that LaTeX in many cases such as [compiling our Julia docs](https://discourse.julialang.org/t/building-julia-documentation-using-typst/97498/3), and new user entry level is much easier. For the same reason I choose Julia for its potential over Python, MATLAB, C++, etc., I prefer Typst for its potential over LaTeX and any TeX derivatives.

That said, like many have pointed out, it’s not yet featured enough to cover many use cases. I sometimes still work with Pluto.jl or MarkDown files over Typst depending on what I need for my task.

---

_[View the full topic](https://discourse.julialang.org/t/typst-and-other-alternatives-to-latex/121652)._