callbag-basics
👜 Tiny and fast reactive/iterable programming library (by staltz)
Cycle.js
A functional and reactive JavaScript framework for predictable code (by cyclejs)
SurveyJS - Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App
With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
surveyjs.io
featured
callbag-basics | Cycle.js | |
---|---|---|
2 | 11 | |
1,653 | 10,235 | |
- | -0.0% | |
0.0 | 4.1 | |
about 1 year ago | 5 months ago | |
JavaScript | TypeScript | |
MIT License | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
callbag-basics
Posts with mentions or reviews of callbag-basics.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-12-28.
-
callbag-rs: Rust implementation of the callbag spec for reactive/iterable programming
p/s: This library is a port of https://github.com/staltz/callbag-basics
-
callbag-rs: An implementation of the callbag spec
This is an attempt at a direct port (including all the same tests) of https://github.com/staltz/callbag-basics
Cycle.js
Posts with mentions or reviews of Cycle.js.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-03-19.
- Could angular possibly compile rxjs Ahead Of Time?
-
Can be the future of JSX be Functional first?
Seems like you might be interested in this
-
Front-end Guide
Cycle
-
[AskJS] Opinions In Favor of Coding Document Fragments in JS?
This is the standard way of going about things in Mithril and Cycle. Elm as well doesn't use an XML knockoff for view code- and as a fun fact, the original version of React didn't either.
- What is a really cool thing you would want to write in Rust but don't have enough time, energy or bravery for?
- Solid.js feels like what I always wanted React to be
-
callbag-rs: An implementation of the callbag spec
For example, an FRP framework (created by the same author who later wrote the callbag spec): https://cycle.js.org/
-
Does it make sense to use Scala.js/Laminar in the context of a startup?
TypeScript is relatively mainstream at this point, and I think that's good news. If you want to crank the type-safety and pure FP dials on it to 11, you certainly can do that. I have a project that I've based largely on this post, including the "hardcore" section. However, instead of Redux and otherwise plain React, I've chosen to use Cycle.js and the lessons from this post to use React in a very purely Functional Reactive Programming Way.
-
Flame: A PureScript front-end framework inspired by the Elm architecture
This post links to a PureScript project that is probably the easiest PS framework around.
ReScript + rescript-react is a good alternative. Less safe, waaaay more verbose; but backed by Facebook.
This is quite cute (in TypeScript though): https://github.com/cyclejs/cyclejs
And Yew is super cool, it goes the WASM route (in Rust): https://github.com/yewstack/yew
-
My Open Source Journey
From now on I was on what I would call a typical open source trajectory. I used the Cycle.js framework to rewrite my frontend and in that process I hit some walls. I eventually figured that the error was on my side and that I was just missing some information to avoid the error. To spare others the hours of debugging I started to contribute small patches to the documentation. At the same time I also found some missing features that I voiced in GitHub issues.