3 ms·
I clicked through to ask this, as well. I appreciated Dioxus directly addressing that in the README, but would also be interested to hear experiences from peop
by veidr 3y ago
I clicked through to ask this, as well.
I appreciated Dioxus directly addressing that in the README, but would also be interested to hear experiences from people with experience using both of them.
With Tauri, I built a toy desktop app to see whether the IPC was fast enough that the web frontend could update and do stuff on every keystroke without lagging (yes), and whether it could send a big file roundtrip from the frontend to the Rust layer and back to the frontend on every keystroke (no, not in my naive toy implementation anyway).
It seems like there's be many use cases where either Tauri or Dioxus would be fine, and some use cases where Dioxus would be better. Would love to hear comparative experiences, or even "we chose Dioxus|Tauri for our project because of X and Y" type stories.
Dioxus looks really cool, and I'm excited to try it.
- jkelleyrtp 3y agoTauri and Dioxus both share a webview and all of Tauri's extensions/plugins work with dioxus, so the only real difference is where your code lives. Since Dioxus and Tauri share a good deal of architecture similarities, it's not really an "either/or" case and I'm sure whatever the Tauri folks try to monetize will work with Dioxus apps automatically.