in-one-weekend VS dioxus

I followed that tutorial as one of my very first Rust projects. Here is my GitHub repo: https://github.com/LoganDark/in-one-weekend

my implementation

I feel like this isn't just a case of people intentionally trying to ignore Rust's idioms, but just not knowing how to transfer over their existing knowledge. As someone who's learned over 15 programming languages throughout the years (rookie numbers, I know ;) it was relatively easy for me to learn Rust in about 2 weeks by diving straight into Ray Tracing in One Weekend (my implementation here), but I still feel like not many people could have done that, so I tend to hold off on assuming that they're intentionally trying to misuse Rust.

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