I keep going back to Tauri, which is practical to build desktop apps quickly but still uses HTML, CSS, JS to build the UI. You can use Rust web UI tools but then it is still (system) browser based.
I keep going back to Tauri, which is practical to build desktop apps quickly but still uses HTML, CSS, JS to build the UI. You can use Rust web UI tools but then it is still (system) browser based.
Unless you were talking about commercial licenses - in that it's not that complicated neither; it's expensive.
It’s not a rust ui system; it’s a declarative ui language that happens to have a rust binding via macros so you can write the custom DSL.
It also has bindings for other languages.
It feels like a bunch of qtquick people got together and implemented a new runtime for qtquick. That might be the direction qt has gone, at the expense of their c++ qtwigets system, but it just feels… “electron app” to me.
If I wanted an electron app, I would just use electron.
If I wanted a non-native ui look and feel, I would use flutter.
What kind of PRs? Like new widget components or what?
Maybe https://github.com/longbridge/gpui-component would be more keen on accepting PRs like that?
So there is now a fork: https://github.com/gpui-ce/gpui-ce/ But I don't know if that's sustainable.
I hope the community fork could gain traction. I believe there's a lot of potential in GPUI.
Failed to open window: WebGPU context not initialized. Was Platform::run() called?
Not being able to load the component gallery does not inspire great confidence.
It's not really designed for the web though so I wouldn't hold that against it.