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

Explanation in README as to why a switch to Redux should be made #255

Open
damassi opened this issue Jun 18, 2015 · 5 comments
Open

Explanation in README as to why a switch to Redux should be made #255

damassi opened this issue Jun 18, 2015 · 5 comments
Labels

Comments

@damassi
Copy link

damassi commented Jun 18, 2015

While I'm excited to make the switch (starting that now) and enjoy the purely functional nature of Redux, it would be nice if you could write out your reasoning behind recommending that users move over. Flummox is great -- it's as simple as it gets, is explicit, with great docs and a large user base -- but Redux is different, and some of the design behind it as well as its patterns might be confusing to new / less experienced users. Perhaps a blog post explaining your thinking would be nice?

@vjpr
Copy link

vjpr commented Jun 19, 2015

The nice sugar of Flummox that we all know and love will be available as a lib over the top of Redux. This is good, keeps the Redux core nice and small. E.g. here is a gist of how to get Flummox-like actions in Redux: https://gist.github.com/vjpr/c9c7cfe405fed8965a51.

I'm in the process of moving from Flummox to Redux. Currently the docs and examples are very lacking, but I expect within a couple of months this will improve.

I did find it strange that a lib with 1000+ stars was recommending a lib with "don't use in production" in its README.

@scott-coates
Copy link

Oh you gotta be kidding me. I just spent several hours today moving from a different, relatively well known flux library to flummox only to come across this 😝

Should I continue move towards implementing flummox or just wait altogether for redux now?

@acdlite
Copy link
Owner

acdlite commented Jun 20, 2015

My weekend project is to re-write/improve the docs for Redux, including a section about how it improves on classical Flux architectures. Once I'm done I'll link to them from Flummox's README.

reduxjs/redux#140

@dlindenkreuz
Copy link

@scoarescoare Same here, go on and enjoy the flummox syntax as long as you can if it gets your job done. That's what I'm going to do.

@bradobro
Copy link

@acdlite Thank you for Flummox! It's brought some clarity and DRY-ness. I deeply reviewed about 10-15 flux frameworks before choosing it, and especially like how you clarified the registration of synchronous and asynchronous handlers. That was a great piece of clarity, that this.register this.handler is the same as this.registerAsync null, this.handler, null really cleared up a lot of my code, and got rid of a lot of actions for starts and fails.

Nice piece of engineering. I hope you'll keep putting hour stuff out there, wherever your attention turns.

I'll be taking a hard look at Redux--thanks for recommendation and your work helping people port.

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

No branches or pull requests

7 participants