leptos

I agree. Incoming hot take. IMO, a big part of it is the lack of competition (in approach) exacerbated by the inability to provide alternatives due to technical/syntactical limitations of JavaScript itself. Vue, Svelte, Angular, Ripple - anything other than React-y JSX based frameworks require custom compilers, custom file-types and custom LSPs/extensions to work with. React/JSX frameworks have preferential treatment with pre-processors essentially baking in a crude compile time macro for JSX transformations. Rust solved this by having a macro system that facilitated language expansion without external pre-processors - e.g. Yew and Leptos implement Vue-like and React-like patterns, including support for JSX and HTML templating natively inside standard .rs files, with standard testing tools and standard LSP support; https://github.com/lept

How would you compare the two (Dioxus and Leptos)? The link to Leptos is https://github.com/leptos-rs/leptos for those who need it.

That sounds valid ideas. Since it's a simple template engine, I avoided adding many features like you mentioned. Maybe, if you want those features, you would love yew and leptos which are other UI frameworks with Rust. https://github.com/yewstack/yew https://github.com/leptos-rs/leptos

Looks like their website is struggling, alt: https://github.com/leptos-rs/leptos

Hmm... I understand that if you don't know anything about the language or what is a flake, it may be a little bit difficult. But really, adding a new package to your environment once you have a flake setup, which a minimal one is trivial, is just adding the name of the package. Here you have a flake.nix example from leptos. https://github.com/leptos-rs/leptos/blob/main/flake.nix You want a new dependency? Add it to buildInputs. (this one doesn't have packages setup, but anything in the attribute set packages will be available in path) You want to search a package: https://search.nixos.org/packages (or use the cli) you want to test a package before adding it? nix-shell -p or nix shell for example. Heck, even if you want it more easy, you could write a tool in less than 100 lines that adds packages names to .json/.yaml/.toml, which allows

Not exactly what you are looking for, probably, but Leptos[1]. Dioxus[1.1], Yew[2] and almost all "frontend web frameworks in rust" run primarily/only on WASM. Larger list here[3] [1] https://github.com/leptos-rs/leptos, https://github.com/dioxuslabs/dioxus [2] https://yew.rs/ [3] https://github.com/flosse/rust-web-framework-comparison#fron...

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 leptos [2]. [1] https://github.com/lambda-fairy/maud [2] https://github.com/leptos-rs/leptos

I think WASM will win. I've been using JavaScript for 25+ years, and I just wrote a SPA using Rust/WASM using the Leptos framework: https://github.com/leptos-rs/leptos, and now I don't want to go back to JavaScript. Cargo is a superior package manager, with Cargo I might actually be able to let me my project sit for a year or two and go back and build to a working runtime without having to do a lot of dependency updates (good luck doing that with NPM). Rust has a solid type system, and with the borrow checker along with pattern exhaustive matching I can write something that I know is solid and will be difficult to break. There is no need to have multiple stages build pipeline running through Babel and Webpack which need to be properly configured; simply compile Rust to the WASM target and that is it. The WASM bundle is also likely to

Not sure if this is of any use: https://github.com/leptos-rs/leptos https://docs.rs/leptos_axum/latest/leptos_axum/

For this there's Leptos and a half dozen other "DOM in Rust" frontend frameworks: https://github.com/leptos-rs/leptos These are already orders of magnitude faster than React, and as the WASM<->DOM bridge improves, they will only get faster. Sycamore: https://github.com/sycamore-rs/sycamore https://sycamore-rs.netlify.app/examples/todomvc/# Dioxus: https://dioxuslabs.com/ In about 3-5 years these frameworks will start to consolidate and reach maturity. It's already possible to build reactive isomorphic apps in Rust. If you haven't checked out Actix/Axum, it feels a lot like Python/Flask. The ecosystem is coming along quickly.