silkenweb VS markup.rs

I hope it's OK to add a shameless plug for my Rust WASM framework, Silkenweb [0]. It's similar to Leptos and Sycamore in that it's signals based, but I've put a lot of effort into making it ergonomic without resorting to a macro DSL. It supports all the usual things like SSR and hydration, along with a few nice extras like scoped CSS.

[0] https://github.com/silkenweb/silkenweb

Silkenweb is able to generate server side HTML, then re-hydrate it on the client from the same code. I'm a bit short on examples at the moment, as I've only just finished that code, but it's just a question of calling hydrate(app) on the client vs something like println!("...{}", app) on the server. What it won't do at the moment is routing on the server, although that's on my list. I've added an issue here to track it. Sycamore and Dioxus may also be options for you.

I'm working on Web Components support for Silkenweb. I've got a couple of the UI5 components working so far.

It was posted yesterday https://github.com/silkenweb/silkenweb

I take a look at https://github.com/silkenweb/silkenweb/blob/main/examples/todomvc/src/main.rs and it seems that it has no persistent storage yet (is this correct, u/simon583?). While other implementations include that, such as https://github.com/lukechu10/maple/blob/master/examples/todomvc/src/main.rs#L135-L145

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