Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Redux perks comparison #31

Open
janat08 opened this issue Feb 7, 2018 · 0 comments
Open

Redux perks comparison #31

janat08 opened this issue Feb 7, 2018 · 0 comments

Comments

@janat08
Copy link

janat08 commented Feb 7, 2018

So according to the blog post: https://medium.com/@dan_abramov/you-might-not-need-redux-be46360cf367 , there're bunch of perks that qualify redux to be used, and I can't tell what would be uniquely redux feature as there's some parity between tide and redux, which of these features could be as easily implemented by tide?

Persist state to a local storage and then boot up from it, out of the box.
Pre-fill state on the server, send it to the client in HTML, and boot up from it, out of the box.
Serialize user actions and attach them, together with a state snapshot, to automated bug reports, so that the product developers can replay them to reproduce the errors.
Pass action objects over the network to implement collaborative environments without dramatic changes to how the code is written.
Maintain an undo history or implement optimistic mutations without dramatic changes to how the code is written.
Travel between the state history in development, and re-evaluate the current state from the action history when the code changes, a la TDD.
Provide full inspection and control capabilities to the development tooling so that product developers can build custom tools for their apps.
Provide alternative UIs while reusing most of the business logic.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant