magikmw

Cargo has you mostly covered for tooling, including tests.

Having just now gotten myself into node at work (after python and rust), I wish I could just use cargo instead of npm and a boatload of packages.

Better get to it then!

Thanks for naming my biggest problem with writing rust code. Every crate has it’s own particular Result chain, doesn’t it. To the point we have anyhow and eyre to help with this mess.

And I agree with that core reason, it’s why I chose dioxus too.

I’ve not bothered with component libraries, as my UI is ironically very simple, but the ecosystem is slowly growing.

For simpler stuff you can use tailwind out of the box with it’s various libs.

I heard dioxus is react-like which tells me barely anything, as I’ve avoided writing any JavaScript in my 15 years of programming, but the rsx components seem intuitive enough for me.

You get a signal framework too, the usual rust examples/ dir is there to show how to do some things.

One thing I struggled with was auth, especially any SSO auth. There’s barely any rust crates for it (and none high level ones), and dioxus docs aren’t straightforward with how to integrate axum middleware. Gotta dig deeper.

For frontend only, it seems great. Other than wasm being a bit of a chunk to download it’s quick, usually well hydrated and the UI seemingly being on one page with no page loads is cool.

I’ve used dioxus a couple of times but I don’t know if I have any general useful insights.

I’ve mostly used it for mobile, which does require a bunch of manual patching.

Fullstack/web seems ok. I like the auto-reload, and obviously rust tooling is relevant.

Any specific questions?