restate
redux-essentials-example-app
restate | redux-essentials-example-app | |
---|---|---|
3 | 37 | |
34 | 294 | |
- | 1.4% | |
6.1 | 0.0 | |
about 1 year ago | 18 days ago | |
TypeScript | CSS | |
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.
restate
- Show HN: Restate – Build reliable back ends using state machines
-
JavaScript State Machines and Statecharts
One quality about state machines that I find overlooked is debuggability. Limiting state updates to transitions makes it so easy to debug weird edge cases and race conditions. This upside is perhaps more relevant on the backend though where state is more long-lived, which is why I've been experimenting with a project for building backends with state machines: https://github.com/fabianlindfors/restate.
- Show HN: Restate – Build understandable back ends with state machines
redux-essentials-example-app
- Redux vs Zustand
- Designing an async app as a long time backend engineer dedicated to synchronous pages. Help!
-
I was struggling with MVx architectures for years and now I can explain why
You're right, it is related. But I think that Flux- and ELM-like architectures are making it even worse by forcing any "external" interaction to became the gap. Look how they suffer when it comes to executing any async operation like network request. Initially we have this relatively simple framework, but then we had to add "Middleware" to just run network request (which is a good example of the Remainder issue). I love the idea behind these architectures, which makes logic more predictable and testing way easier. I even was using them by myself. But now they looks like something turned inside out for me. I believe we could do better. I'm finishing my proposal right now. It will take couple more weeks to edit and translate it, but soon I'll show what I mean.
-
JavaScript State Machines and Statecharts
Hi, I maintain Redux and wrote most of our docs (including our current tutorials).
Can you give some details on which parts of our docs you feel are "incomprehensible"? I'm curious which specific pages you've been looking at, and for what purpose.
We've tried to organize the docs using the "Documentation System" approach described at [0]: Tutorials for teaching step-by-step, Explanations and How-To guides for specific topics, and References for API details.
Generally we want people to go through our "Redux Essentials" tutorial [1] as the primary way to learn how to use Redux correctly. It teaches "modern Redux" patterns with Redux Toolkit as the standard way to write Redux logic (including RTK Query for handling data fetching), and React-Redux hooks in components.
I'm genuinely interested in feedback on what explanations aren't clear and how we can improve things!
[0] https://documentation.divio.com/
[1] https://redux.js.org/tutorials/essentials/part-1-overview-co...
- Best React Course 2023 (intermediate / advanced)
- Redux vs Redux toolkit
-
Redux, RTK, React Query, Typescript resources
https://redux.js.org/tutorials/essentials/part-1-overview-concepts (covers how to use Redux Toolkit and RTK Query)
- I don't get why I should use Redux
- What library or tool is causing you the most pain right now?
- Beginner’s guide to Redux