sycamore-mac
rust-signals
sycamore-mac | rust-signals | |
---|---|---|
3 | 6 | |
8 | 588 | |
- | - | |
0.0 | 4.5 | |
over 2 years ago | 21 days ago | |
Rust | Rust | |
- | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
sycamore-mac
-
A first look at Sycamore's new reactive primitives: how the next version of Sycamore will be the most ergonomic yet
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.
-
How's the GUI-creation side of Rust looking nowadays?
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.
-
Tauri – Electron alternative written in Rust
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
rust-signals
-
A Proposal for an asynchronous Rust GUI framework
What is the relation and differences between this approach and rust-signals?
-
A good/decently matured rxjs-based library?
Signals is a fantastic and stable library for reactive programming https://github.com/Pauan/rust-signals
-
A first look at Sycamore's new reactive primitives: how the next version of Sycamore will be the most ergonomic yet
How does this approach differ from rust-signals? https://github.com/Pauan/rust-signals
-
Announcing avalanche 0.1, a React- and Svelte-inspired GUI library
You might want to check out dominator and the rust-signals it is based on, seems like a similar technique to avalanche.
-
Crate similar to Kotlin Flow?
Maybe try futures-signal? I think its API looks quite nice and it even has a tutorial.
-
Rust on the front-end
Both are signal-based, which seems like the way to go to me. The latter seems more mature in terms of code, but also lacking in good documentation. The rust-signal crate it uses though has a nice tutorial from which a lot of concepts seem to transfer.
What are some alternatives?
dioxus - Fullstack GUI library for web, desktop, mobile, and more.
rust-dominator - Zero-cost ultra-high-performance declarative DOM library using FRP signals for Rust!
DomTerm - DOM/JavaScript-based terminal-emulator/console
sycamore - A library for creating reactive web apps in Rust and WebAssembly
proxy-polyfill - Proxy object polyfill
salsa - A generic framework for on-demand, incrementalized computation. Inspired by adapton, glimmer, and rustc's query system.
xplorer - Xplorer, a customizable, modern file manager
differential-dataflow - An implementation of differential dataflow using timely dataflow on Rust.
webview - Tiny cross-platform webview library for C/C++. Uses WebKit (GTK/Cocoa) and Edge WebView2 (Windows).
avalanche - Rust library for building performant Web apps
iced - A cross-platform GUI library for Rust, inspired by Elm
observe - Rust observables inspired by MobX