markup.rs VS template-benchmarks-rs

(Sailfish is fastest, but it's syntax is of the more traditional <%= msg %> flavour and Markup.rs is second-fastest with a Maud-like syntax but the author apparently doesn't have time to rewrite the syntax reference, so you have to follow a link from the open issue to an old version of the README.)

Maud or markup.rs for templating (I use the latter, and it is faster, but they're both fast and markup.rs is currently missing its full syntax documentation unless you dig through the revision history for the stale version. I'd recommend the former for you.)

For the sake of thoroughness, I should point out that Haml-like templating engines like Maud and markup.rs are even more concise.

https://maud.lambda.xyz/ or https://github.com/utkarshkukreti/markup.rs for server-side HTML templates that compile to Rust code

(eg. In Python, Genshi templates are too slow for me to feel comfortable using them, but they were the main way to get robust correctness checks for templates last time I evaluated my options. In Rust, Markup.rs or Maud are the second and third fastest templating solutions, as I remember, and they give even more well-formedness guarantees for HTML than Genshi.)

There are various templating solutions that use syntax derived from the host language, like Maud or markup.rs for Rust, the E factory API for lxml for Python, etc.

You can have similar features to Phoenix Live View by using Turbo from Hotwire with your favorite template engine in Rust. Contrary to what the video presentation on the Hotwire main page leaves you to believe, Hotwire works with any template engine from any language, not just Rails. Markup.rs and Turbo from Hotwire should compose quite nicely.

Any recommendations for rust template engines? I'd like something that can easily render labeled fragments of a template instead of requiring me to split a page into a dozen little files. Kinda like inline {{block}} definitions in Go's html/template. Speed is also nice.

From template-benchmark-rs [0] I found sailfish [1] (fast, but no fragments(?)). render-rs [2] and syn-rsx [3] (2022) both let you write html in rust macros which is cool (maybe that can substitute for fragments?). Then there's gtmpl-rust [4] which is just Go templates reimplemented in rust.

[0]: https://github.com/rosetta-rs/template-benchmarks-rs

[1]: https://github.com/rust-sailfish/sailfish

[2]: https://github.com/render-rs/render.rs last updated Jul 2020

[3]: https://github.com/stoically/syn-rsx last updated Nov 2022

[4]: https://github.com/fiji-flo/gtmpl-rust

Personally, I'd recommend Maud if you don't need something with runtime reloading. Not only is it much faster, it implements a template language that is effectively the Rust-syntax equivalent to Slim or Haml using a procedural macro, so you get compile-time verification that your HTML output is well-formed.

I've been maintaining several benchmark repos based off of template-benchmarks-rs. I've noticed there are several other benchmark repos that are hard to know about.

I'm tempted to collect all of these benchmark repos into a github org to make them easier to find. So far I know of parser, md, argparse, and template languages.

Simple and straightforward. The only thing I'd change personally is using sailfish over markup. Seems to be the fastest templating engine?

As I said in my other post, runtime performance wasn't a concern for me except to catch anything egregious, like mini_markdown hanging. If people want to expand on this with different representative cases and criterion like template-benchmarks-rs, they are welcome to!

That's why I use Sailfish for server-side templating in my Rust web projects. It's ridiculously fast.

As for templating, here's a benchmark that can double as a list of candidates to choose from... though, again, Rust stuff tends to be fast, so don't assume that the slowest templating engine on a Rust-vs-Rust benchmark is going to be slow.

Yeah. You're much better off worrying about template rendering performance or database query optimization than the framework itself.