gui-thunks
incremental-rs
gui-thunks | incremental-rs | |
---|---|---|
2 | 1 | |
3 | 13 | |
- | - | |
10.0 | 7.8 | |
about 4 years ago | 3 months ago | |
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.
gui-thunks
-
Humble Chronicles: Managing State with Signals
It's interesting how every build system, frontend framework, programming language implements its own promise pipeline/delayed execution/observables/event propagation.
But the implementations are rarely extracted out for general purpose usage and rarely have a rich API.
I've been thinking a lot about a general purpose "epoll" which be registered on objects that change. I want to be able to register a reaction to a sequence of actions on arbitrary objects with an epoll style API.
One of my ideas is GUI thunking. The idea that every interaction with the GUI raises a new type that can be interacted with, to queue up behaviours on the GUI. This is essentially Future<> that are typed and the system reacts to the new type based on what you did.
It's a bit like terraform plan and apply, but applied to general purpose GUIs.
For example, you can click download file, then queue up installation and then using the application, ALL BEFORE it is installed. Because the actual computation is separate from the type information that was queued up.
Imagine using AWS Console to set up an entire infrastructure and wire everything together but not actually execute anything until the very end when you click "Run".
https://github.com/samsquire/gui-thunks
-
Programming Breakthroughs We Need
I spend everyday thinking of what my computer could be doing.
Most of the time the CPU is waiting for IO - memory, network, SSD, disk and not doing any work.
You might like my idea called GUI Thunking.
https://github.com/samsquire/gui-thunks
incremental-rs
-
Humble Chronicles: Managing State with Signals
May be of interest: I released a port of Incremental to Rust the other week. It has a bit of a way to go in polish and docs, but the core implementation and API should be very familiar. It has Expert nodes so incremental-map is feasible and already works. I’ve been using it as the state management for some UI with much success. Credit to the authors because it’s a good design. https://github.com/cormacrelf/incremental-rs
What are some alternatives?
signal - Functional Reactive Programming implementation for Rust
bgjs
dylint - Run Rust lints from dynamic libraries
wasmtalk - Personal WebAssembly learning project (build a SmallTalk like environment but with WASM)
ReactiveUI - An advanced, composable, functional reactive model-view-viewmodel framework for all .NET platforms that is inspired by functional reactive programming. ReactiveUI allows you to abstract mutable state away from your user interfaces, express the idea around a feature in one readable place and improve the testability of your application.
c4-notation - Technical resources for using the C4 model for visualizing software architecture.
sdk-java - Temporal Java SDK
MyDef - Programming in the next paradigm -- your way
S - S.js - Simple, Clean, Fast Reactive Programming in Javascript
language-server-protocol - Defines a common protocol for language servers.
additive-gui