crank
rust-signals
crank | rust-signals | |
---|---|---|
13 | 6 | |
2,673 | 588 | |
0.1% | - | |
8.1 | 4.5 | |
9 days ago | 23 days ago | |
TypeScript | Rust | |
MIT License | 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.
crank
-
Coroutines in JavaScript for Web Components
If you enjoy this approach, you might enjoy the Crank JS framework. https://crank.js.org/
> Crank uses generator functions to define stateful components. You store state in local variables, and `yield` rather than `return` to keep it around.
- Crank.js, the Just JavaScript Framework
-
A Proposal for an asynchronous Rust GUI framework
I'm very interested in seeing if using the commonly implemented forms of compiler support for async programming can also be well used for GUI programming. One wishawa[0] is also perusing this approach in Rust but I first came upon this idea from the crank-js[1] authors. It wasn't clear to me why that one never went anywhere. Was it failure with the approach or was React just a good solution in the space? I can say this though, there's something strikingly elegant about those initial samples of using JavaScript generators for components.
[0]: https://github.com/wishawa/async_ui
[1]: https://github.com/bikeshaving/crank
Take a look at crank.js, a JavaScript framework where components can be written as async functions or as generators. It seems similar to what you're trying to do :)
- UnsuckJS: Progressively enhance HTML with lightweight JavaScript libraries
-
Algebraic Effects – You Can Touch This (2019)
Well there's https://crank.js.org that uses native js generators where you would you normally put hooks in. Never used it but looked like a very neat idea.
-
What happens if you mix React, Mobx and generators*? Ok, let's do it!
Reminds me of https://github.com/bikeshaving/crank, which was rather fun for a PoC I made a while back.
-
Are my components supposed to render multiple times?
Strictly speaking, the framework hides this complexity away, but it still exists and it is the framework that's now paying the extra cost. Of course a framework is allowed, and should, when possible, hide away these things. For example Crank.js uses generators to allow for async Components as first class citizens, https://github.com/bikeshaving/crank, but they're still having to deal with the pitfalls of asynchronous work.
-
React State Museum - Examples to help portray the how, why, which, pros, and cons of various state management systems in the React ecosystem
To give the author of https://crank.js.org/ due credit, after reading through the descriptive posts I was impressed by the amount of thought and design that went into it.
-
What's New in React 18?
> What do you propose as an alternative?
There are lots of alternatives, but perhaps the simplest would have been to use async generators. This is how Crank[0] (mentioned elsewhere in this thread) works, and it allows you to do anything (AFAIK) that's possible with hooks with a much simpler and more testable API.
> So, sure, there are limitations and rules you have to pay attention to with hooks... but that's just programming.
No, it's not. The biggest problem with React hooks is that they are not composed of transferable knowledge, meaning memorizing these rules and patterns does not transfer outside of React; likewise, I can't use much of the knowledge I have already built up over many years of my career when using hooks. It's the same argument that's made against Rails, where you have to learn tons of Rails-specific idioms (on top of having to understand general concepts like relational database access patterns) instead of just writing code in a way that's more direct and intuitive for anyone.
My brain has limited RAM. The more things I have to keep in my head when developing against an API, the more likely I am to make a mistake. With every release of React, I seem to have to keep more and more of these details in my brain as I work. Contrast this with something like Svelte, where you really only need to fully grok about two concepts to use it effectively. I understand that this is the tradeoff the React team made, but I'm not convinced it's worth it.
[0]: https://crank.js.org/ and https://crank.js.org/blog/introducing-crank
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?
js-framework-benchmark - A comparison of the performance of a few popular javascript frameworks
rust-dominator - Zero-cost ultra-high-performance declarative DOM library using FRP signals for Rust!
React - The library for web and native user interfaces.
sycamore - A library for creating reactive web apps in Rust and WebAssembly
async_ui - Lifetime-Friendly, Component-Based, Retained-Mode UI Powered by Async Rust
salsa - A generic framework for on-demand, incrementalized computation. Inspired by adapton, glimmer, and rustc's query system.
ava - Node.js test runner that lets you develop with confidence 🚀
sycamore-mac
sucrase - Super-fast alternative to Babel for when you can target modern JS runtimes
differential-dataflow - An implementation of differential dataflow using timely dataflow on Rust.
solid - A declarative, efficient, and flexible JavaScript library for building user interfaces.
avalanche - Rust library for building performant Web apps