Personally very intrigued by Dioxus. I posted this thread the other day about frontend and I can't help but be drawn by the possibility of not having to learn a JS/TS framework and instead go with a Rust framework. But at the same time, Dioxus is still very much behind on the ecosystem side because it doesn't have access to all the libraries and tools and support and online help that popular JS/TS frameworks do. So I'm sort of conflicted. Being a frontrunner comes at a cost sometimes 😅

Only thing I actually don't care much about with Dioxus is the fullstack premise. I'm not much for the fullstack idea. I think there is value in separating the backend and frontend. I feel like in principle it should be possible for many frontends to exist for a single backend. I feel the fullstack approach makes the backend and frontend too coupled and it would probably be hard to write a different frontend for the backend.

[–] alex_is@infosec.exchange 2 points 4 days ago

@SorteKanin I realize that cost too. I''d love to run Rust up and down my stack. But JS is very much still king unfortunately. The sheer breadth of materials, mature frameworks and libraries make it the prudent choice. But the documentation/example part is something I feel deeply. I remember struggling with iced.rs when I had to use it. Sure, there were examples, but it was a complete shift in thinking and implementing complex widgets and visuals was really hard. I felt a lot of similarities to that when I tried Dioxus. It is a terrific framework, it just needs time to mature, as does pretty much ever front end Rust framework.

load more comments (3 replies)