dioxus

In, my opinion it's good for ambitious projects to have a stable financial foundation. What negative things one project does because of venture capital does not mean another will. There's no CLA. Dioxus is MIT/Apache-2 licensed. > How many of the contributors are directly payed for their contributions? I unfortunately feel like you're asking this in bad faith. Our team is very small, we're very lean, and we have funding sources that aren't just venture. We also have a very active community and people are building new libraries and becoming dioxus contributors every day. https://github.com/DioxusLabs/dioxus/releases/tag/v0.6.0 (scroll to contributors)

Yes, Sciter is definitely pretty close. We think we can do better CSS support. Sciter has good CSS2 layout support, but only has it's own proprietary equivalent to Flexbox. Our CSS2 support is currently pretty patchy, but we have good Flexbox and CSS Grid support. We also have full support for things like media queries and css variables which I don't believe Sciter supports. Regarding "just disable the JS": You can, but then you won't have scripting support. Blitz still has scripting support without JS using https://github.com/DioxusLabs/dioxus which is a react-like UI framework but in Rust.

We have a web components example here: https://github.com/DioxusLabs/dioxus/blob/fd21c971038840130f... Everything should work like normal except: attributes are not typed, custom event listeners must be implemented with web-sys

Wrote about that here: https://github.com/DioxusLabs/dioxus?tab=readme-ov-file#diox... You're probably not going to be building an email client or the next instagram in egui, but it is good for stuff where you're fine with re-rendering every entire frame (data viz, graphics stuff).

Creator here, so I'm biased... Yew has had about 10 commits in the past 6 months and the original creator has since moved on. Leptos is a good solution for web-app type stuff, but IMO there's a big usability gap. I'll let the community be the judge there, but I wrote up some differences here: https://github.com/dioxusLabs/dioxus/?tab=readme-ov-file#dio... Leptos was fortunate enough to receive a lot of attention from youtubers on its launch. The most important thing here: we raised venture money for Dioxus. We have many years of runway, are pretty lean, and exclusively focused on pouring resources into making the best GUI library for Rust (and potentially branching out to Python/JS). Getting into YC isn't easy, raising money isn't easy, and there's currently no other Rust projects with similar goals, talent, and financial backing. Biased

Wrote about that here in our readme: https://github.com/dioxusLabs/dioxus/?tab=readme-ov-file#dio... Tauri puts your frontend in the webview and you need to communicate with native Rust functions through an IPC boundary (like electron). In Dioxus your Rust code lives on the native side, so you don't need IPC to do things like read from the file system, websockets, etc. Tauri also forces your frontend to compile to WASM, and a lot of interesting rust crates don't compile to wasm. It's a little hard to express how much simpler it is to build when you don't have an IPC boundary. Dioxus' tooling is also dedicated to just Rust, so you can go from zero to bundled `.app` in less than a minute (12 seconds fresh build, 20 seconds fresh bundle). That being said we're huge fans of Tauri and the flexibility it gives you (frontend in whatever web-comp

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