The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning. Learn more →
Starfx Alternatives
Similar projects and alternatives to starfx
-
flet
Flet enables developers to easily build realtime web, mobile and desktop apps in Python. No frontend experience required.
-
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.
-
hamilton
Hamilton helps data scientists and engineers define testable, modular, self-documenting dataflows, that encode lineage and metadata. Runs and scales everywhere python does.
-
fastapi-azure-auth
Easy and secure implementation of Azure Entra ID (previously AD) for your FastAPI APIs 🔒 B2C, single- and multi-tenant support.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
starfx reviews and mentions
-
FastUI: Build Better UIs Faster
Ah! A real criticism of FE development, I agree with your problem statement.
When you jump into the world of single-page applications, things get complex pretty quickly, because the use case for needing an SPA pushes the web app into a full desktop application.
Ultimately, for a highly interactive and dynamic "desktop-class" user experience, there is added complexity. I think that's why so much movement within the FE world has moved away from "SPA for everything" and into these mixed dynamic apps. Islands, React Server Components, NextJS, they all help create a middleground between a document-based website with no dynamic elements with a full blown desktop app experience. They all have real tradeoffs, in particular adding an entirely new backend service to serve the front end.
For many projects, react + react-query is probably enough.
Having said that, my argument from https://bower.sh/dogma-of-restful-api still stands: when you build an API that is RESTful (1:1 mapping between endpoint and entity) you are unknowingly pushing the complexity of data synchronization to the FE, which requires a well thought out ETL pipeline.
This probably doesn't help my case but I've been building a simplified middle-layer for react to bridge the gap between react-query and full blown SPA: https://starfx.bower.sh
- Show HN: Starfx – A modern approach to side-effect and state management in UI
-
Effection 3.0 – Structured Concurrency and Effects for JavaScript
`redux-saga` maintainer here.
I've been using `effection` to build a replacement for `redux-saga` over at https://github.com/neurosnap/starfx
Effection has demonstrated to me how truly powerful delimited continuations are and why structured concurrency is an incredible asset for anything that requires async flow control -- basically everything in TS/JS.
I know sometimes it's hard to imagine why someone would need structured concurrency or care about delimited continuations for a front-end application, but this is a game changer in terms of expressing async flow control.
Some things to note about Effection:
- API surface area is small https://github.com/thefrontside/effection/issues/851
- It tries to stay as close to JS constructs as possible so it will feel very familiar
- Resource cleanup is automatic (when a function passes out of scope all descendent tasks are shut down automatically)
- End-user doesn't need to think about delimited continuations
The only leap users need to "deal with" coming from async/await is the syntax.
import { main, call } from "effection";
-
Internals of Async / Await in JavaScript
- https://github.com/thefrontside/continuation
- https://github.com/thefrontside/effection/tree/v3
- https://github.com/neurosnap/starfx
The last one intends to replace redux-saga using DCs.
Here’s a presentation I gave recently talking about DCs in typescript: https://youtu.be/uRbqLGj_6mI?si=XI0JNMKMoO2VHMvM
-
Philosophy of Coroutines
A couple of us have been experimenting with deliminited continuations and I think it’s gonna take off soon:
https://youtu.be/uRbqLGj_6mI?si=kgKKjpCnehJ9bpIG
https://github.com/neurosnap/starfx
-
Observable API Proposal
I feel the same way which is why I decided to help maintain the project. Async flow control is very tricky even in js–land. Having watchers live inside of a while-loop is a powerful construct that lends itself to interest flow control patterns.
I'm also in the process of rebuilding redux-saga but without the redux part: https://github.com/neurosnap/starfx
It's still in alpha stage, but it is very reminiscent of redux-saga.
-
A note from our sponsor - WorkOS
workos.com | 28 Apr 2024
Stats
neurosnap/starfx is an open source project licensed under MIT License which is an OSI approved license.
The primary programming language of starfx is TypeScript.
Sponsored