klask VS sycamore-mac

There are also similar applications for usage with clap-rs.[1][2]

[1]: https://github.com/MichalGniadek/klask

[2]: https://github.com/grantshandy/claui

This is what https://github.com/MichalGniadek/klask was made for.

Klask is another GUI generator for clap that uses egui, but claui and klask work in different ways. Klask runs your code by running itself as a child with an environment variable to ignore its GUI, then capturing the child stdout. Claui only runs one process; it spawns your code in another thread and then reroutes all of your stdout into a buffer on each frame through shh.

If you want a simple GUI over command line tools, things like klask make that really easy.

Not inherently, but practically yes – currently. There are attempts to use it for desktop ui https://github.com/Submersible/sycamore-mac but in general nothing prevents you from using it as you like and implement a backend you need.

Sycamore. And before people start complaining that it's just a webview or a browser in disguise, I would like to add that Sycamore was built from the start to allow multiple render backends. Right now, there are only backends for DOM and SSR (Server Side Rendering) but it should be pretty easy to extend it to native UI frameworks. In fact, there is a POC here of Sycamore running on macOS: https://github.com/Submersible/sycamore-mac although it is right now far from usable.

I used this a bit, it was really great. Writing a Rust backend & exposing it to TypeScript was really slick!

There was one issue I ran into that made me think about jumping to Electron mid project, but I can't remember what it was now, but I think it was something like making my app bleed the entire MacOS window while still being moveable.

The other downside is you're going to be tempted to go down the rabbit hole and do everything in Rust. [1]

[1] https://github.com/Submersible/sycamore-mac