If you're specifically interested in @recoiljs, the last 3 videos walk through how refactor a reducer using recoil, and finally, how to refactor form atoms and atomFamilys into something works like the reducer+dispatch pattern:
youtube.com/watch?v=RFIfJ-Vz…
Hey #JavaScript and #React community, @ReactLiveNL is coming up, join us virtually on September 11th, 2020!
I'll be speaking on @RecoilJS and hosting a free beginner-level workshop: "Building a React Site from Scratch" for ticket holders.
For tickets:
reactlive.nl
Just confirmed our @reactiflux Q&A schedule for the next few months!
Sept 3rd - @mcc_abe author of Recoil
Oct 1st - @dabit3 author of React Native in Action and DevRel @AWSAmplify@awscloud
Dec 16th - @radiomorillo author of The Developers Guide to Content Creation & much more
Been working on a React project for my part-time job, and finally hit the point where I needed to add some kind of state across different components.
Decided to give @recoiljs a try, as it seemed incredibly light and the API conforms to existing conventions.
I’m impressed!
You can even structure your store such that old URLs and state can be upgraded to newer app state trees. So you can support legacy links. What's the use case? It kicks ass for read-only BI Dashboards, Data Viz, Monitoring, and Visual Analysis tools
More dank...
Recoil has first-class support for snapshots and store observation as well as URL and localStorage persistence. Meaning you can serialize the entire store to a shareable, bookmarkable URL.
You can also use it for read-only data fetching. This is extremely underrated, yet powerful feature. Recoil lets you define async data dependencies via selectors/atoms (weird names for sure). Then can compose them like React to define how data should be refetched....
Recoil tl;dr
Recoil adds another state tree outside of React. Instead of keeping one object + reducer like Redux, Recoil lets you colocate updates in components w/ a useState-like API. It is very useful when React.useReducer is too slow.