sailfish VS markup.rs

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

Sailfish (very fast, but lots of unsafe usages)

(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.)

Using [Actix](actix.rs/), Sailfish, thiserror, and a bunch of supporting libraries reminds me of when I was building a project using Pylons and Mako (now replaced with Pyramid), except without the SQL.

If you're OK with a template engine that can't be used in any sort of "if debug builds, support hot reloading" mode, Sailfish compiles its templates to native code and it's the fastest option around.

(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.