markup.rs VS maud

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

I would like to mention maud in this context:

https://github.com/lambda-fairy/maud

It is refreshingly different from other Rust templating libraries. It uses a proc-macro that compiles your HTML into Rust code. I also happen to use it in conjunction with HTMX and it works very well for me (at least in small projects).

You can also use HTML templating with crates like askama, tera and maud! This can be combined with the power of lightweight JavaScript libraries like htmx to speed up time to production. You can read more about this on our other article about using HTMX with Rust which you can find here.. We also collaborated with Stefan Baumgartner on an article for serving HTML with Askama!

I think a lot of us reach for Jinja-style templates so it feels a little more like we're writing bare HTML. But they're of course still just templates, and they need a build step before they become valid HTML.

So it's true, if you're willing to use a DSL embedded in your server language (like JSX), then you'll have the full language tooling available to you. And this probably isn't giving up much over language-specific templates.

A JSX-equivalent for the Rust server-side rendering world would probably be maud [1] or leptops [2].

[1] https://github.com/lambda-fairy/maud

[2] https://github.com/leptos-rs/leptos

Maud as a performant templating engine that will ensure your templates are well-formed at compile-time and, in effect, minify the generated HTML output by not passing through unnecessary whitespace.

Maud is a fast Slim/Haml-esque templating engine which will automatically minify your HTML at no extra charge because whitespace isn't significant in its syntax.

If you want to do backend development, give actix-web or Axum a try. If you need templating, take a look at Maud and if you want an ORM, take a look at SeaORM.

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.

For templating, Maud is fast, gives compile-time well-formedness guarantees, and outputs minified HTML by default as a side-effect of it being based on Rust macros. (It's of a similar design philosophy to Slim and Haml)