I'm glad I have the opportunity to reinforce the statements in this post. I can say without a doubt that starfx is an implementation that is as clean as it is powerful.
At Softwiz, we have important production modules, which aggregate real business data of significant volume, written with starfx.
I have followed the library's development since its inception, as it naturally follows from saga-query, providing a logical and seamless progression.
Personally, I take great pleasure in writing code using "thunks," and I believe the technique challenges you to be more imaginative without being restrictive.
For instance we can centralize the logic into thunks or apis, from different sources like IPC, workers, UI or the store itself. This allows us to combine or derive everything in an elegant manner.
The familiarity comes, I think, from the database metaphor where we are used to work with tables views and queries and Starfx translates those concepts in JavaScript.
From here roots a philosophy of handling effects, following the natural thought process for when we are managing data flows.
I wanted to show-off something I've been working on for the better part of a year. At Aptible, we have been using starfx in production for a few months now with great success.
At Softwiz, we have important production modules, which aggregate real business data of significant volume, written with starfx. I have followed the library's development since its inception, as it naturally follows from saga-query, providing a logical and seamless progression.
Personally, I take great pleasure in writing code using "thunks," and I believe the technique challenges you to be more imaginative without being restrictive.
For instance we can centralize the logic into thunks or apis, from different sources like IPC, workers, UI or the store itself. This allows us to combine or derive everything in an elegant manner.
The familiarity comes, I think, from the database metaphor where we are used to work with tables views and queries and Starfx translates those concepts in JavaScript.
From here roots a philosophy of handling effects, following the natural thought process for when we are managing data flows.