proposal-signals
S
| proposal-signals | S | |
|---|---|---|
| 3 | 9 | |
| 2,806 | 1,229 | |
| 4.9% | - | |
| 9.0 | 0.0 | |
| 14 days ago | over 1 year ago | |
| TypeScript | JavaScript | |
| 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.
proposal-signals
-
A Proposal to Add Signals to JavaScript: A Mistake?
Recently, there's been a buzz about a proposal to introduce Signals to JavaScript. But before diving in, what exactly is a signal?
-
Updates from the 101th TC39 meeting
Signals: A declarative programming model for updating based on changes to state.
- Proposal to Add Signals to JavaScript
S
-
Proposal: Signals as a Built-In Primitive of JavaScript
Related is S.js: https://github.com/adamhaile/s
I love signals. I prefer them when making UIs over any other primitive (besides, perhaps, the cassowary constraint algorithm). I try to replicate them in every language I use, just for fun.
I also don't believe they belong in the Javascript language whatsoever. Let the language be for a while, people already struggle to keep up with it. TC-39 is already scaring away people from the language.
-
Humble Chronicles: Managing State with Signals
"Signal" has been used in FRP circles for some time [1,2]. The original FRP stuff was events/signals and behaviours. But I agree that JS didn't use this terminology until more recently. S.js is maybe one of the earlier ones, but that was still over 8 years ago.
[1] https://scholarworks.rit.edu/cgi/viewcontent.cgi?article=651...
[2] https://github.com/14427/signal
[3] https://github.com/adamhaile/S/tree/e897ec1212a073bb1fe695e1...
-
Super Charging Fine-Grained Reactive Performance
Fine-grained reactivity libraries have been growing in popularity recently. Examples include new libraries like Preact Signals, µsignal, and now Reactively, as well as longer-standing libraries like Solid, S.js, and CellX. Using these libraries, programmers can make individual variables and functions reactive. Reactive functions run automatically, and re-run 'in reaction' to changes in their sources.
-
Answering Common Questions about Krestianstvo SDK 4
No. Krestianstvo SDK 4 is introducing its own implementation of Croquet Application Architecture in JavaScript, based on Solid JS & S.js using Functional Reactive Programming (FRP).
- Introducing Preact Signals: a reactive state primitive that is fast by default
-
Krestianstvo SDK 4 | Implementing Croquet and Recursive Portals on Solid JS
SolidJS / S.JS
-
Show HN: A tiny (850B) and fast reactive observables library via functions
Cool! This reminds me of S.js [0] which I've used a decent amount to great effect, but it seems about half the size. I'll have to look at how they compare (though if someone knows off the top of their head that'd be appreciated). S.js is nice because it has a helper library (surplus) for dom things.
[0]: https://github.com/adamhaile/S
-
Writing a reactive library in Javascript [from scratch]
There are a lot of good libraries and frameworks to handle state management and reactivity. From simple and short utilities such as S.js to heavy solutions like Solid.
-
JavaScript is whats wrong with JavaScript :)
except that is wrong... you're welcome.
What are some alternatives?
valup
oby - A rich Observable/Signal implementation, the brilliant primitive you need to build a powerful reactive system.
incremental-rs
racket-gui-easy - Declarative GUIs in Racket.
krestianstvo - Krestianstvo SDK 4 is the OSS implementation of Croquet architecture in functional reactive paradigm using Solid JS. For developing serverless collaborative and multiplayer applications.
cellx - The ultra-fast implementation of reactivity for javascript
vwf - Virtual World Framework
ui - experimental ui component library for the browser
bruh - The thinnest possible layer between development and production for the modern web.
flimsy - A single-file <1kb min+gzip simplified implementation of the reactive core of Solid, optimized for clean code.
usignal - A blend of @preact/signals-core and solid-js basic reactivity API
solid - A declarative, efficient, and flexible JavaScript library for building user interfaces.