gtk4-cross VS sycamore

I use it from rust, it works with libadwaita. Since it's rust I just run cargo in a docker container. https://github.com/MGlolenstine/gtk4-cross

(Assuming GTK4) For Windows you could try gtk4-cross. It was pretty clunky to use for Vala but since they have a Rust-specific image it should be easier for your use case

For gtk programs I just put the dll's in the same folder as the binary and distribute it as a zip. Not the most elegant, but it works. I use this docker image to do the bundling https://github.com/MGlolenstine/gtk4-cross

If you're willing to install docker it's really easy to build and package for windows. https://github.com/MGlolenstine/gtk4-cross

I'm guessing you're not using this Docker container? → https://github.com/MGlolenstine/gtk4-cross

You can just bundle the required DLL's in the same directory as the executable. They don't need to install anything. You can use this docker container to handle the bundling automatically for you https://github.com/MGlolenstine/gtk4-cross

With gtk4 you can just bundle the libs. You can check out https://github.com/MGlolenstine/gtk4-cross for a docker container that handles cross-compiling to windows and packaging the libs.

The image for cross compiling: gtk4-cross

Yeah, it's actually much easier to cross compile from linux to windows. If you only have windows you can use docker desktop and this container to cross compile https://hub.docker.com/r/etrombly/rust-crosscompile . It doesn't have gtk4 support yet though, someone forked it if you need gtk4 https://github.com/MGlolenstine/gtk4-cross

Perseus is a fast frontend web development framework for Rust with built-in support for reactivity using Sycamore, server-side rendering, and much more. Sycamore is a frontend library that allows you to build interactive user interfaces with Rust. I’d say that Perseus is to Sycamore as Next.js is to React, so it’ll be helpful for you to have a fair understanding of Sycamore before jumping into using Perseus — although it’s not necessary to follow along in this article.

Now, I considered whether to spend more time fixing everything that now failed in sycamore 0.9. But there are major changes ahead which would require yet another major refactoring, to the point where I am not sure whether it would not be more of a rewrite than a refactoring, given my previous experiences with sycamore.

Sycamore.

Sycamore, Yew, or Seed if you want a full-stack solution. (Or Leptos if you want something that's faster but less mature.)

There are others, like Sycamore, similar story as Leptos but imo Leptos is (currently) more ergonomic.

Sycamore is a reactive library for creating web apps in Rust and WebAssembly. https://github.com/sycamore-rs/sycamore

I tried my first project with yew as frontend. And my experience was after some time similar to the already mentioned ones: It is a little more to take on than I actually wanted. And some things were not straightforward to achieve. I switched to sycamore for the other projects now and I am much more satisfied (but this could also be since I have some more experience in the Rust ecosystem by now). Changing from yew to sycamore was pretty easy and I can achieve most of the tasks with less code.

If you want to do fullstack/SPA stuff, check out Sycamore, Seed, and Yew.

If you want to do front-end SPA development, take a look at Yew, Seed, or Sycamore.

I have written a front-end (website) application in Rust that is used internally in production. I wouldn't recommend to use something like sycamore, leptos, dioxus, yew for you next puplic web-app now but i can absolutely see how this is used in the future as those libs mature.