Choo VS dioxus

I haven't used elm much, but I do like elm quite a bit! I actually wrote a JS framework inspired by the "elm architecture" a few years back (choo). Admittedly I never looked at how they do CSS though. Is the elm-css package the right thing to look into?

I'm currently working on a way to extend the code by revealing the underlying [Choo](https://choo.io) framework to enable easier hacking! Search is one feature that theoretically won't be too hard to add, but I excluded it from the core because it would have made it too big.

Note: I have no solid reference point for what "too big" actually means for this project—my only guideline so far has been "as small as possible"

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