bubbletea VS dioxus

I recommend looking at the charm libraries. Lip gloss https://github.com/charmbracelet/lipgloss can provide the styling and bubble tea can handle the screen updates and framework https://github.com/charmbracelet/bubbletea there is a premade progress bar component in bubbles library. https://github.com/charmbracelet/bubbles

I built a TUI app to find anime scenes by image to learn the TUI framework [Bubbletea](https://github.com/charmbracelet/bubbletea)

TUI’s are awesome; I’ve used this library to build them in the past: https://github.com/charmbracelet/bubbletea

For a sufficiently-complex system, a CLI client just isn’t as powerful as a live “console”. A TUI can play the part and you don’t have to venture into the web SPA world.

If you want to build terminal app, I highly recommend the bubbletea library: https://github.com/charmbracelet/bubbletea

You can view your snippets in a human-friendly web UI that syntax-highlights the code and even renders markdown. In addition to the Web UI, the TUI (powered by bubbletea) has a file browser, code viewer and attribute editor.

A sibling comment points at https://github.com/charmbracelet/bubbletea as a Go alternative with a similar architecture

The closest thing in Go I know about is bubbletea:

https://github.com/charmbracelet/bubbletea

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