techhub.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A hub primarily for passionate technologists, but everyone is welcome

Administered by:

Server stats:

5.3K
active users

#dioxus

0 posts0 participants0 posts today

Petite mis-à-jour du tableau de borde "mon département" pour le baromètre vélo.
L'entête a changé un peu, et affiche désormais le total des réponses dans le département (ou le préfixe choisi en tout cas)
Merci aux utilisateur·ice·s pour les retours, ça fait du bien! 😊

barometre.toulon-var-deplaceme

github.com/black-puppydog/baro

#rustlang #dioxus #tailwind #var #toulon #france #baromètreVélo2025 #vélo #fub
/cc @fub @tvd

I'm reading the #dioxus intro material to relax (😅 German election day) and I'm wondering:

If the server side functions expand to #axum routes on the backend... Say I want authentication or some such for these routes, would that be easy?

I've been using axum for my toy project anyhow, and was gonna integrate a dioxus toy project with the resulting API. But would it be possible to build everything as one fullstack dioxus app, and have the result still be usable as a stand-alone API?

I would like to give #rust a try for a web frontend using #Wasm. I want something that has painless (like the #Elm Architecture) state management. I saw #Dioxus and #Yew but state management looks like the same mess than in React. It seems that Sauron github.com/ivanceras/sauron/ could do the job, but there is no way to interact with JS (maybe not needed ?). Any feedback?

A versatile web framework and library for building client-side and server-side web applications - ivanceras/sauron
GitHubGitHub - ivanceras/sauron: A versatile web framework and library for building client-side and server-side web applicationsA versatile web framework and library for building client-side and server-side web applications - ivanceras/sauron
Replied in thread

If you were to start a reactive-UI #RustLang application soon, and desktop wasn’t important. Web only, ideally full stack. Hot reloading would be great. Using tailwind for styles. Wasm load time is negligible here, and JS/TS to be avoided.

Would you then:
- wait for #Leptos 0.7?
- go with #Dioxus 0.5 (or wait for 0.6? I don’t know their roadmap so well)?
- or choose something completely different?

@chrisbiscardi