tectonic VS crates.io

You may want to try https://github.com/tectonic-typesetting/tectonic, which downloads files from TeXLive on-demand.

v2 has improved TeX engine lookup, improved PDF template look&feel, proper support for MS Windows (where it comes integrated with the Tectonic engine) and a few more new features.

There's https://github.com/tectonic-typesetting/tectonic but I think the issue with that idea is that sure, you can re-implement TeX (it's sufficiently simple) in Rust and then run LaTeX packages on top of it, but then you're back to LaTeX and all its weirdness so you haven't really gained anything compared to LaTeX itself.

In terms of TeX, I would recommend taking a look at tectonic, a self-contained TeX distribution that auto-installs packages you need when you need them, and “just works” when you call the binary to compile… Because screw messing around with package managers, CTAN and XeTeX. I’ve been using it for around a year and it’s so much easier than any other TeX distribution.

For example, you can have your main application in something like Deno/Node/python that acts as a server, and then delegate the actual pdf generation to tectonic (https://github.com/tectonic-typesetting/tectonic) or Typst https://typst.app/blog/2023/beta-oss-launch/

tectonic: https://github.com/tectonic-typesetting/tectonic

How does it compare with Tectonic?

It's sad that Tectonic conversion to Rust[1] was never finished. For now it's just a wrapper around C and C++ code. By far, it was the most promising thing in this distribution.

[1] https://github.com/tectonic-typesetting/tectonic/issues/459

The only thing I've seen is https://github.com/tectonic-typesetting/tectonic but that's an actual re-implementation of TeX Rust.

Rust has a rich ecosystem of frameworks and libraries that let you read, parse, and manipulate text files, interact with cloud services and databases, and perform any other job that your project's development workflow may require. And because of its strong typing and tight memory management, you are much less likely to write programs that behave unexpectedly in production.

All the code discussed in this article can be accessed through this repository. For integration with existing projects consider using keyword_extraction crate available on crates.io.

So, be sure to double-check your critical libraries and be sure their alternatives exist in the Rust ecosystem. There’s a good chance the crates you need are available in Rust's crates.io repository.

The previous section was very simple, this section is also very simple but introduces us to cargo which is Rust's package manager, as a JS dev my mind goes straight to NPM.

Now, there has to be a place where all these packages come from. Similar to npmjs registry, where all node packages are registered, stored and retrieved, Rust also has something called crates.io where many helpful packages and dependencies are registered.

Before proceeding, let's check https://crates.io/, the official Rust package registry.

The most thrilling aspect has been the joy of writing the backend. It's like every struct, enum, and method in Rust forms this interconnected Multiverse of code , which you can see in crates.io which is best Documentation experience I Ever Had.

5. Crates.io

When using crates from eg. crates.io, and also things like std and core

Vendoring your packages was very tedious to even remotely get to work with Cargo. I spent a very long time getting Cargo to work together with cargo-local-registry. We vendor crates from crates.io and a custom internal registry.