perseus VS dioxus

The best part is that it doesn’t use a virtual DOM for its reactivity, which can lead to a significant increase in performance.  Perseus not only inherits some of the best aspects of existing web frameworks but also strives to surpass them. Perseus went stable on April 9, 2023 after one year of beta development -- this is just the beginning!

I actually made a small sample project some weeks ago using Axum + Perseus + Sycamore. The purpose was to show, that also unocss was possible instead of tailwindcss. But I recommend tailwindcss for now, because there is an easy to use Perseus Plugin for it. https://gitlab.com/kibsi-perseus-examples/perseus-sycamore-rest-example-unocss But it could maybe be of interest to you. There are also the official Perseus examples: https://github.com/framesurge/perseus/tree/main/examples/core

Perseus is a web development framework for the Rust programming language. https://framesurge.sh/perseus/en-US/

Perseus is a pure Rust web development framework with support for static site generation, server-side rendering, client-side rendering, reactive state, internationalization, capsules (sometimes called an 'islands architecture'), seamless deployment, custom API routes, and so much more! And, after a year of beta versions, v0.4.0 of it just went stable!

Personally, I would go for Perseus. https://framesurge.sh/perseus/en-US

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

I think something like https://dioxuslabs.com could deliver native, cross platform apps and win back mobile.

While we took an in-depth look at Dioxus in this tutorial, there is still so much to learn. Luckily, Dioxus provides detailed documentation with references and cookbooks to guide developers. Make sure you check it out, and feel free to comment below with any questions.

You can probably imagine the challenges of integrating such a system in a robust way that does a good job and improves on the status quo. We felt like the Tauri implementation worked well for Tauri apps. But there’s a problem: it was so tightly coupled to Tauri that the work couldn’t be enjoyed by other projects (not even the ones like Dioxus who were using Tauri’s underlying technology of Tao + Wry).

Floneum is a graph editor for local AI workflows. It uses llm to run large language models locally, egui, and dioxus for the frontend, and wasmtime for the plugin system. If you are interested in the project, consider joining the discord, or building a plugin for Floneum in rust using WASI