Live data from Hacker News

RaTeX: KaTeX-compatible LaTeX rendering engine in pure Rust

ratex.lites.dev

21–30 of 114 posts

Re: RaTeX: KaTeX-compatible LaTeX rendering engine in pure Rust

#21

I used LaTeX for approximately 10 years, for little things to relatively complex, including my bachelor’s and master’s theses. It never felt natural at reliable or consistent. Every customization required weird \makeatletter \makeatother hacks and was very brittle. Everything seemed more complicated than necessary and hard to grok, with weird interdependencies and interactions. There are probably good reasons for all…

[dead]

Re: RaTeX: KaTeX-compatible LaTeX rendering engine in pure Rust

#22
post #17

I used LaTeX for approximately 10 years, for little things to relatively complex, including my bachelor’s and master’s theses. It never felt natural at reliable or consistent. Every customization required weird \makeatletter \makeatother hacks and was very brittle. Everything seemed more complicated than necessary and hard to grok, with weird interdependencies and interactions. There are probably good reasons for all…

Is Typst appropriate for web apps; e.g., the input forms here?

Nope. Typst's primary output is PDF, and it is a stand-alone binary. It's a replacement for most uses of LaTeX to produce documents. It is not a replacement for this project, which focuses only on rendering LaTeX math code and can be embedded in multiple different runtimes.

Re: RaTeX: KaTeX-compatible LaTeX rendering engine in pure Rust

#23
post #16

I used LaTeX for approximately 10 years, for little things to relatively complex, including my bachelor’s and master’s theses. It never felt natural at reliable or consistent. Every customization required weird \makeatletter \makeatother hacks and was very brittle. Everything seemed more complicated than necessary and hard to grok, with weird interdependencies and interactions. There are probably good reasons for all…

You want Typst: https://github.com/typst/typst It's like the JSX of Latex: markup in a programming language, not a programming language pretends to be markup.

> I used Typst for a few weeks. It already feels much more understandable, consistent, hackable, and customizable. I guess that is the difference between an ad hoc macro system and an actually thought through programming language.

> The only drawback I can see is the ecosystem being smaller and less mature. That is, however, counteracted by being able to do things on your own, without immersing yourself deeply in LaTeX for years. Also, it will improve with time.

Re: RaTeX: KaTeX-compatible LaTeX rendering engine in pure Rust

#24

The landing page (clearly to a large part written by LLM) does not mention that both KaTeX and mathjax can render to SVG in node. This wasm approach might still be lighter, but the advantage is not as clear as the page makes it seem. (It also contains LLM dishonesties like that the bundle size is 0 KB.)

Where this clearly wins is native rendering use cases where there is no browser or JS engine involved at all.

Re: RaTeX: KaTeX-compatible LaTeX rendering engine in pure Rust

#26

I used LaTeX for approximately 10 years, for little things to relatively complex, including my bachelor’s and master’s theses. It never felt natural at reliable or consistent. Every customization required weird \makeatletter \makeatother hacks and was very brittle. Everything seemed more complicated than necessary and hard to grok, with weird interdependencies and interactions. There are probably good reasons for all…

I’ve been using Typst for years now. Wrote my PhD thesis in it [1] as well as a book. Works great; can’t recommend it enough. I usually barely use plugins because it’s either already included or pretty easy to write a bit of code yourself

[1]: https://github.com/rikhuijzer/phd-thesis

Re: RaTeX: KaTeX-compatible LaTeX rendering engine in pure Rust

#27

I used LaTeX for approximately 10 years, for little things to relatively complex, including my bachelor’s and master’s theses. It never felt natural at reliable or consistent. Every customization required weird \makeatletter \makeatother hacks and was very brittle. Everything seemed more complicated than necessary and hard to grok, with weird interdependencies and interactions. There are probably good reasons for all…

It's kinda fascinating how dominant LaTeX is, how nice its output is, how respected Knuth is as a computer scientist, and at the same time how totally awful it feels to use it. Hard to figure out how it can be so good and so bad at once.

Posts/discussion I found interesting:

- http://www.goodmath.org/blog/2008/01/10/the-genius-of-donald...

- https://tex.stackexchange.com/q/24671

- https://news.ycombinator.com/item?id=15733381

In particular it's interesting how people seem to think TeX itself is actually quite nice to use but its popularity and LaTeX packages created a huge mess of a system.

Re: RaTeX: KaTeX-compatible LaTeX rendering engine in pure Rust

#28

I used LaTeX for approximately 10 years, for little things to relatively complex, including my bachelor’s and master’s theses. It never felt natural at reliable or consistent. Every customization required weird \makeatletter \makeatother hacks and was very brittle. Everything seemed more complicated than necessary and hard to grok, with weird interdependencies and interactions. There are probably good reasons for all…

This mirrors my experience. It's worth noting that TeX was developed in the same time period that the details of lexical scope were being nailed down by Guy Steele in the Rabbit compiler for Scheme. It's not that TeX is an ad hoc system; it's more the case that people didn't actually know how to implement a better system at the time.

'People' in this case were Don Knuth (TeX) and Leslie Lamport (LaTeX). Both are Turing Award winners.

Re: RaTeX: KaTeX-compatible LaTeX rendering engine in pure Rust

#29

I used LaTeX for approximately 10 years, for little things to relatively complex, including my bachelor’s and master’s theses. It never felt natural at reliable or consistent. Every customization required weird \makeatletter \makeatother hacks and was very brittle. Everything seemed more complicated than necessary and hard to grok, with weird interdependencies and interactions. There are probably good reasons for all…

Huh. My special lady friend is in the process of finishing up her thesis using LaTeX after ditching LibreOffice. It was nightmare for some of the same reasons: bad UX, bad portability and crippling bugs. There was a ramping up period, and she had an out of date GitHub repo to help her, but she is incredibly happy that she switched. Collaboration could be smoother I guess.

Re: RaTeX: KaTeX-compatible LaTeX rendering engine in pure Rust

#30
post #2

Interesting. Reminds me of Typst (both implemented in Rust and replacing TeX to some degree) and Microtex.

I've discovered typst in the last year and used to build a resume and cover letter template that feeds from a YAML file.

After a bit of tinkering and understanding the idiosyncracies of Typst, the joy of having reliable, consistent, beautiful, data-driven resumes and cover letters is not measurable. It basically lifted any barrier to applications, while whatever I had before I had always considered a burden.

On top of that, I can add hiring process data directly to the yaml file to run further analysis.

Can LaTeX do this? Most probably, but the learning curve is the difference.

Post reply on HN