#dioxus — Public Fediverse posts

Well, it took a few weeks but I feel I finally understand how dioxus wants you to build a full stack app. And now implementing things is waaay easier and fun!

#rustlang #rust #dioxus

So I have read some more about the whole #dioxus vs #tauri plus #leptos plus #axum for a #rust #rustlang #desktop app.

From what I read by now, I would say that I will try the tauri route next. I would still prefer if Dioxus would just work, but what makes me wary about whether Dioxus would be a sustainable choice is that there's a lot of issues in the Dioxus repository that do not even have a reply by a maintainer. My own issues (which are relatively young!) have only little interaction. I get that this is an open source project and maintainer overload and so on, sure. But there's also something about Dioxus being funded? So there are full-time devs (plural!) working on it? What can I say? This makes me wary.

Going down that tauri route would mean that I would need to build the whole thing myself. That could work, but is more than I would have liked to do. I want to develop my app functionality, not set up a GUI development environment.

I could also go for a TUI first, but tbh, I would rather like to have a GUI first, with a clean API that I can then reuse to build a TUI on top of it. Not sure why, the other way around would probably work as well 🤔.

Either way, I would then try leptos as framework for the app, because it looks rather good from what I can read from its documentation, and I can use axum in the backend, which I think fits my needs as well. (Btw developing this with ratatui with a axum backend would also be possible, but that's not the "native way" for a ratatui app, but much more for a leptos app as I understand it, so I expect less headaches here).

I hope I can get a MVP fast, so I can get back to developing my core application stuff, because there's sooo much missing still.

So I have read some more about the whole #dioxus vs #tauri plus #leptos plus #axum for a #rust #rustlang #desktop app.

From what I read by now, I would say that I will try the tauri route next. I would still prefer if Dioxus would just work, but what makes me wary about whether Dioxus would be a sustainable choice is that there's a lot of issues in the Dioxus repository that do not even have a reply by a maintainer. My own issues (which are relatively young!) have only little interaction. I get that this is an open source project and maintainer overload and so on, sure. But there's also something about Dioxus being funded? So there are full-time devs (plural!) working on it? What can I say? This makes me wary.

Going down that tauri route would mean that I would need to build the whole thing myself. That could work, but is more than I would have liked to do. I want to develop my app functionality, not set up a GUI development environment.

I could also go for a TUI first, but tbh, I would rather like to have a GUI first, with a clean API that I can then reuse to build a TUI on top of it. Not sure why, the other way around would probably work as well 🤔.

Either way, I would then try leptos as framework for the app, because it looks rather good from what I can read from its documentation, and I can use axum in the backend, which I think fits my needs as well. (Btw developing this with ratatui with a axum backend would also be possible, but that's not the "native way" for a ratatui app, but much more for a leptos app as I understand it, so I expect less headaches here).

I hope I can get a MVP fast, so I can get back to developing my core application stuff, because there's sooo much missing still.

So I have read some more about the whole #dioxus vs #tauri plus #leptos plus #axum for a #rust #rustlang #desktop app.

From what I read by now, I would say that I will try the tauri route next. I would still prefer if Dioxus would just work, but what makes me wary about whether Dioxus would be a sustainable choice is that there's a lot of issues in the Dioxus repository that do not even have a reply by a maintainer. My own issues (which are relatively young!) have only little interaction. I get that this is an open source project and maintainer overload and so on, sure. But there's also something about Dioxus being funded? So there are full-time devs (plural!) working on it? What can I say? This makes me wary.

Going down that tauri route would mean that I would need to build the whole thing myself. That could work, but is more than I would have liked to do. I want to develop my app functionality, not set up a GUI development environment.

I could also go for a TUI first, but tbh, I would rather like to have a GUI first, with a clean API that I can then reuse to build a TUI on top of it. Not sure why, the other way around would probably work as well 🤔.

Either way, I would then try leptos as framework for the app, because it looks rather good from what I can read from its documentation, and I can use axum in the backend, which I think fits my needs as well. (Btw developing this with ratatui with a axum backend would also be possible, but that's not the "native way" for a ratatui app, but much more for a leptos app as I understand it, so I expect less headaches here).

I hope I can get a MVP fast, so I can get back to developing my core application stuff, because there's sooo much missing still.

So I have read some more about the whole #dioxus vs #tauri plus #leptos plus #axum for a #rust #rustlang #desktop app.

From what I read by now, I would say that I will try the tauri route next. I would still prefer if Dioxus would just work, but what makes me wary about whether Dioxus would be a sustainable choice is that there's a lot of issues in the Dioxus repository that do not even have a reply by a maintainer. My own issues (which are relatively young!) have only little interaction. I get that this is an open source project and maintainer overload and so on, sure. But there's also something about Dioxus being funded? So there are full-time devs (plural!) working on it? What can I say? This makes me wary.

Going down that tauri route would mean that I would need to build the whole thing myself. That could work, but is more than I would have liked to do. I want to develop my app functionality, not set up a GUI development environment.

I could also go for a TUI first, but tbh, I would rather like to have a GUI first, with a clean API that I can then reuse to build a TUI on top of it. Not sure why, the other way around would probably work as well 🤔.

Either way, I would then try leptos as framework for the app, because it looks rather good from what I can read from its documentation, and I can use axum in the backend, which I think fits my needs as well. (Btw developing this with ratatui with a axum backend would also be possible, but that's not the "native way" for a ratatui app, but much more for a leptos app as I understand it, so I expect less headaches here).

I hope I can get a MVP fast, so I can get back to developing my core application stuff, because there's sooo much missing still.

So I have read some more about the whole #dioxus vs #tauri plus #leptos plus #axum for a #rust #rustlang #desktop app.

From what I read by now, I would say that I will try the tauri route next. I would still prefer if Dioxus would just work, but what makes me wary about whether Dioxus would be a sustainable choice is that there's a lot of issues in the Dioxus repository that do not even have a reply by a maintainer. My own issues (which are relatively young!) have only little interaction. I get that this is an open source project and maintainer overload and so on, sure. But there's also something about Dioxus being funded? So there are full-time devs (plural!) working on it? What can I say? This makes me wary.

Going down that tauri route would mean that I would need to build the whole thing myself. That could work, but is more than I would have liked to do. I want to develop my app functionality, not set up a GUI development environment.

I could also go for a TUI first, but tbh, I would rather like to have a GUI first, with a clean API that I can then reuse to build a TUI on top of it. Not sure why, the other way around would probably work as well 🤔.

Either way, I would then try leptos as framework for the app, because it looks rather good from what I can read from its documentation, and I can use axum in the backend, which I think fits my needs as well. (Btw developing this with ratatui with a axum backend would also be possible, but that's not the "native way" for a ratatui app, but much more for a leptos app as I understand it, so I expect less headaches here).

I hope I can get a MVP fast, so I can get back to developing my core application stuff, because there's sooo much missing still.

Does #dioxus work for anyone for a desktop #linux app?

#rustlang #rust

Ok, so as #dioxus does not work at all, I am going down the "just let's do a web app" route. There's no way the whole thing could be used sensibly as a web app, but hey... First get it working, then get it nice, I suppose.

I tried to get a VERY basic #dioxus app working for about 6 hours now. To no avail.

I try to run a simple stream that counts to 100 in the server and the client should render a "loading percentage" from that.

But the client only receives the first two messages and then just hangs and does not continue.

I don't know why.

And of course, joining their discord to ask them is not possible because FUCKING discord wants me to verify my account again and again... I re-logged in for about 8 times now, verified my email again and again, but these SHITHEADS over at discord just won't let me join another "server".
Searching for the dioxus discord in their search did not help, clicking on "join" there just does nothing.

If there were not expensive hardware on my desk, I would flip the table right now.

FUCKING SHIT!

Building 890 dependencies... okay, thanks #dioxus haha

RE: https://hachyderm.io/@edfloreshz/116180713530512866

This is one of the most frustrating aspects of #Dioxus for me.

While it is undoubtedly one of the best #Rust UI frameworks available, I wish it didn’t heavily rely on web-related concepts and terminology for its syntax and functionality.

I acknowledge this is one of the most appealing aspects of the framework for most, but not for me.

Built a full-stack Rust web app entirely with Claude Code. Claude wrote all the code, I just directed the features, architecture and tech.

Stack:
- Axum with async-graphql API
- Dioxus WASM frontend
- ReDB database

It's an artillery calculator for the game Foxhole — place markers on maps, get firing solutions with wind compensation.

Feel free to check it out: https://arty.dp42.dev
Source code on my github

#Rust #WASM #Dioxus #Axum #AI #ClaudeCode #OpenSource #GameDev

Built a full-stack Rust web app entirely with Claude Code. Claude wrote all the code, I just directed the features, architecture and tech.

Stack:
- Axum with async-graphql API
- Dioxus WASM frontend
- ReDB database

It's an artillery calculator for the game Foxhole — place markers on maps, get firing solutions with wind compensation.

Feel free to check it out: https://arty.dp42.dev
Source code on my github

#Rust #WASM #Dioxus #Axum #AI #ClaudeCode #OpenSource #GameDev

Built a full-stack Rust web app entirely with Claude Code. Claude wrote all the code, I just directed the features, architecture and tech.

Stack:
- Axum with async-graphql API
- Dioxus WASM frontend
- ReDB database

It's an artillery calculator for the game Foxhole — place markers on maps, get firing solutions with wind compensation.

Feel free to check it out: https://arty.dp42.dev
Source code on my github

#Rust #WASM #Dioxus #Axum #AI #ClaudeCode #OpenSource #GameDev

Built a full-stack Rust web app entirely with Claude Code. Claude wrote all the code, I just directed the features, architecture and tech.

Stack:
- Axum with async-graphql API
- Dioxus WASM frontend
- ReDB database

It's an artillery calculator for the game Foxhole — place markers on maps, get firing solutions with wind compensation.

Feel free to check it out: https://arty.dp42.dev
Source code on my github

#Rust #WASM #Dioxus #Axum #AI #ClaudeCode #OpenSource #GameDev

Built a full-stack Rust web app entirely with Claude Code. Claude wrote all the code, I just directed the features, architecture and tech.

Stack:
- Axum with async-graphql API
- Dioxus WASM frontend
- ReDB database

It's an artillery calculator for the game Foxhole — place markers on maps, get firing solutions with wind compensation.

Feel free to check it out: https://arty.dp42.dev
Source code on my github

#Rust #WASM #Dioxus #Axum #AI #ClaudeCode #OpenSource #GameDev

Today I found a TUI for managing translations! 💯

🗂️ **lingora** — A localization management tool for Fluent translation files

🌀 Detect missing/redundant translations + validate dioxus-i18n usage

🦀 Written in Rust & built with @ratatui_rs

⭐ GitHub: https://github.com/nigeleke/lingora

#rustlang #ratatui #tui #i18n #localization #fluent #dioxus #devtools #terminal

#Dioxus has so many great tools! These include use_context for providing a context to all children of a component or use_resource for asynchronous resource loading.
It is just very well integrated, and RSX feels surprisingly elegant, even a bit more readable than XML syntax in my opinion.

#rust #frontend #programming

For a quick test of #dioxus I implemented a web interface for #faup-rs, you can see the demo website (all running locally in webasm) https://faup.claudex.be/

cc @qjerome

https://codeberg.org/claudex/faup-rs

#rust #faup-web

For a quick test of #dioxus I implemented a web interface for #faup-rs, you can see the demo website (all running locally in webasm) https://faup.claudex.be/

cc @qjerome

https://codeberg.org/claudex/faup-rs

#rust #faup-web

For a quick test of #dioxus I implemented a web interface for #faup-rs, you can see the demo website (all running locally in webasm) https://faup.claudex.be/

cc @qjerome

https://codeberg.org/claudex/faup-rs

#rust #faup-web

For a quick test of #dioxus I implemented a web interface for #faup-rs, you can see the demo website (all running locally in webasm) https://faup.claudex.be/

cc @qjerome

https://codeberg.org/claudex/faup-rs

#rust #faup-web

For a quick test of #dioxus I implemented a web interface for #faup-rs, you can see the demo website (all running locally in webasm) https://faup.claudex.be/

cc @qjerome

https://codeberg.org/claudex/faup-rs

#rust #faup-web

I am re-writing Zentrox' frontend for the second time, this time in Rust :rust_ferris: using Dioxus!
I built this small login screen using Dioxus components and Tailwind. I think it is amazing that you can write full-stack applications in one compiled language.

Dioxus: https://dioxuslabs.com
Zentrox [WIP]: https://github.com/wervice/Zentrox

#rust #dioxus #frontend #fullstack #programming

It's insane how much RAM the #nextjs server consumes compared to the #rustlang api. I basically have 0 traffic, and the VM where they run has just 1GB of ram. I wonder if #dioxus would be any different 🤔

There's #ratatui #dioxus #yew #leptos and so on and so forth...

You know what I wonder? Why are there no libraries for full views for any of those? Like... A complete thing I can import to have a view to analyze the logging of my app (there's only one for Ratatui, but I haven't found something like that for the others).

Or a View for analyzing traces, something like Tracy, that I can import and embed in my app.

Or a view that I can embed to have a full WYSIWYG editor?

For all of these, there are only some component libraries for dropdown elements or whatever, but nothing that gives me a whole view of something.

#rust #rustlang

There's #ratatui #dioxus #yew #leptos and so on and so forth...

You know what I wonder? Why are there no libraries for full views for any of those? Like... A complete thing I can import to have a view to analyze the logging of my app (there's only one for Ratatui, but I haven't found something like that for the others).

Or a View for analyzing traces, something like Tracy, that I can import and embed in my app.

Or a view that I can embed to have a full WYSIWYG editor?

For all of these, there are only some component libraries for dropdown elements or whatever, but nothing that gives me a whole view of something.

#rust #rustlang

There's #ratatui #dioxus #yew #leptos and so on and so forth...

You know what I wonder? Why are there no libraries for full views for any of those? Like... A complete thing I can import to have a view to analyze the logging of my app (there's only one for Ratatui, but I haven't found something like that for the others).

Or a View for analyzing traces, something like Tracy, that I can import and embed in my app.

Or a view that I can embed to have a full WYSIWYG editor?

For all of these, there are only some component libraries for dropdown elements or whatever, but nothing that gives me a whole view of something.

#rust #rustlang

There's #ratatui #dioxus #yew #leptos and so on and so forth...

You know what I wonder? Why are there no libraries for full views for any of those? Like... A complete thing I can import to have a view to analyze the logging of my app (there's only one for Ratatui, but I haven't found something like that for the others).

Or a View for analyzing traces, something like Tracy, that I can import and embed in my app.

Or a view that I can embed to have a full WYSIWYG editor?

For all of these, there are only some component libraries for dropdown elements or whatever, but nothing that gives me a whole view of something.

#rust #rustlang

There's #ratatui #dioxus #yew #leptos and so on and so forth...

You know what I wonder? Why are there no libraries for full views for any of those? Like... A complete thing I can import to have a view to analyze the logging of my app (there's only one for Ratatui, but I haven't found something like that for the others).

Or a View for analyzing traces, something like Tracy, that I can import and embed in my app.

Or a view that I can embed to have a full WYSIWYG editor?

For all of these, there are only some component libraries for dropdown elements or whatever, but nothing that gives me a whole view of something.

#rust #rustlang

🔐 Ferrocrypt: a tiny, easy-to-use, highly secure multi-platform encryption tool written in Rust — with both a CLI and GUI apps (Tauri + Dioxus). Symmetric + hybrid encryption modes included.

https://github.com/alexylon/ferrocrypt

#rust #rustlang #cryptography #opensource #cli #tauri #dioxus

@lorax I'm using this to build Debian packages in the @Codeberg CI run, e.g. in these repositories:

https://codeberg.org/pib/pib-service

https://codeberg.org/pib/pibtool

Going one step further, I even do build #wasm artifacts with #dioxus and create packages from that here:

https://codeberg.org/pib/pib-viewer

packages: https://codeberg.org/pib/-/packages

live demo: https://wels.showcase.gemeindetransparenz.at - very early prototype stage and in German only

Beware that these packages don't comply with official #Debian policy though!

@gemeindetransparenz

Fiz um teste com o #dioxus em uma poc e realmente é uma ferramenta sensacional. O que prometem abaixo realmente é entregue. Achei de uma coesão gigantesca e pretendo usar em um projeto que cairá na minha mão em alguns dias.

I've been tinkering on a Discord-inspired native #Matrix client on and off for the past three years. During this time it has gone back and forth between #Slint and #Dioxus, because Slint is always lacking one specific feature (this time rich text rendering, which is coming in the next release apparently) and Dioxus requires a fullblown webview. I finally got to try out the #Servo based modular dioxus-native / blitz and it works amazingly well for my existing dioxus code already!

#Rust #RustLang

O__o

The #tauri + #yew example setup just works... now I think I will play a bit with this and see whether it gets me somewhere, if #dioxus does not work out of the box, it might be a viable alternative? 👀 🤔

O__o

The #tauri + #yew example setup just works... now I think I will play a bit with this and see whether it gets me somewhere, if #dioxus does not work out of the box, it might be a viable alternative? 👀 🤔

O__o

The #tauri + #yew example setup just works... now I think I will play a bit with this and see whether it gets me somewhere, if #dioxus does not work out of the box, it might be a viable alternative? 👀 🤔

O__o

The #tauri + #yew example setup just works... now I think I will play a bit with this and see whether it gets me somewhere, if #dioxus does not work out of the box, it might be a viable alternative? 👀 🤔

O__o

The #tauri + #yew example setup just works... now I think I will play a bit with this and see whether it gets me somewhere, if #dioxus does not work out of the box, it might be a viable alternative? 👀 🤔

Hey #nixos #nixpkgs community... Has someone successfully set up a #dioxus dev env?

I tried to get #dioxus running for about two hours now, just open the freakin default generated example app as a desktop app on wayland.

Does not work.

Great development experience you have there!

I’m learning Rust and have been building Ferrocrypt, a small cross‑platform encryption tool (Rust core lib + CLI + Dioxus GUI + Tauri GUI).

It uses XChaCha20‑Poly1305 + Argon2id and a hybrid RSA+XChaCha20 mode with Reed–Solomon parity for header recovery.

I’d really appreciate a code review (lib/CLI/GUI, error handling, idiomatic Rust).

Repo: github.com/alexylon/Ferrocrypt

#rust #rustlang #rustaceans #dioxus #tauri #cryptography #infosec

I’m learning Rust and have been building Ferrocrypt, a small cross‑platform encryption tool (Rust core lib + CLI + Dioxus GUI + Tauri GUI).

It uses XChaCha20‑Poly1305 + Argon2id and a hybrid RSA+XChaCha20 mode with Reed–Solomon parity for header recovery.

I’d really appreciate a code review (lib/CLI/GUI, error handling, idiomatic Rust).

Repo: github.com/alexylon/Ferrocrypt

#rust #rustlang #rustaceans #dioxus #tauri #cryptography #infosec

I’m learning Rust and have been building Ferrocrypt, a small cross‑platform encryption tool (Rust core lib + CLI + Dioxus GUI + Tauri GUI).

It uses XChaCha20‑Poly1305 + Argon2id and a hybrid RSA+XChaCha20 mode with Reed–Solomon parity for header recovery.

I’d really appreciate a code review (lib/CLI/GUI, error handling, idiomatic Rust).

Repo: github.com/alexylon/Ferrocrypt

#rust #rustlang #rustaceans #dioxus #tauri #cryptography #infosec

I've spent the last 3 weeks writing #rust on the frontend with #dioxus and it's been super smooth sailing. I'm not a frontend person but this has been by far the most developer friendly experience I've had in a while. Especially compared to most modern react frameworks.

🦀 Dioxus v0.7.0 is released - Hot-patching of Rust code at runtime - Fullstack: Revamp of Server Functions with full Axum integration - WGPU-based HTML/CSS renderer for Dioxus - tailwind support And more github.com/DioxusLabs/d... #rustlang #dioxus

1/ I went in an event to learn about “ #Amazon Q Developer” platform to build my dev network.
Besides the fact that it’s just another #Claude wrapper in a #VScode clone 🤢 it was basically a “workshop” in #Vibe-coding.

I thought “Ok, fine, I’ll have it build a #Dioxus app…”

It failed, hard.

I spent the last 3 months writing an app with Kotlin & Jetpack Compose Multiplatform. Every, single, step was a battle. It got to a point last week where I was trying to implement a simple event stream (for time travel in musical compositions) and it was just so needlessly difficult I ditched the entire app completely.

I picked up #Dioxus after a few hours of searching for an alternative. Night and freaking day. I get to write Rust, cross platform and a familiar framework (it's like React)

WIN

Trying out one of the latest demos in the Dioxus repo showcasing the Blitz renderer — pretty wild!
#dioxus #rust

Hot patching #RustLang code? In my #BevyEngine?

https://github.com/bevyengine/bevy/pull/19309 was just merged!
Thanks to subsecond from #Dioxus, coming to Bevy 0.17, and already on main!