rui VS sycamore

Inspired by Xilem, Leptos and rui, Floem aims to be a high performance declarative UI library with minimal effort from the user.

My rui library can render UIs at 120fps, uses similar SDF techniques (though uses a single shader for all rendering): https://github.com/audulus/rui

Is their GPUI library open source?

I think the jury is still out on whether rust is good or bad for UI. Once rust UI libraries are more mature we'll get a sense of it. There are some advantages of static typing, even for UI (see SwiftUI for example). I'll grant the pickiness of rust can be a challenge. Anyway give us some time to work on stuff.

Here's my effort: https://github.com/audulus/rui

rui

Depending on the scale of your project, I could suggest rui library which is cross platform though it's not related to gtk, https://github.com/audulus/rui, It's inspired by swiftUI

I've done a library for vector graphics on the GPU which works pretty well for my uses:

https://github.com/audulus/vger

and a rust version:

https://github.com/audulus/vger-rs

(which powers my rust GUI library: https://github.com/audulus/rui)

Here's the approach for rendering path fills. From the readme:

> The bezier path fill case is somewhat original. To avoid having to solve quadratic equations (which has numerical issues), the fragment function uses a sort-of reverse Loop-Blinn. To determine if a point is inside or outside, vger tests against the lines formed between the endpoints of each bezier curve, flipping inside/outside for each intersection with a +x ray from the point. Then vger tests the point against the area between the bezier segment and the line, flipping inside/outside again if inside. This avoids the pre-computation of Loop-Blinn, and the AA issues of Kokojima.

It works pretty well, and doesn't require as much preprocessing as the code in the article. Also doesn't require any GPU compute (though I do use GPU compute for some things). I think ultimately the approach in the article (essentially Piet-metal, aka tessellating and binning into tiles) will deliver better performance, and support more primitives, but at greater implementation complexity. I've tried the Piet-metal approach myself and it's tricky! I like the simpler Shadertoy/SDF inspired approach :)

You should look into rui, https://github.com/audulus/rui It is an amazing ui Library for rust

Try rui https://github.com/audulus/rui, It's a Swift Type ui

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.