-
Notifications
You must be signed in to change notification settings - Fork 114
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
Use Redux #253
Comments
Why? |
I'm going back to vanilla flux until this bloodbath is over. |
You might be on to something @kswope. Ive spent a day and a half trying to decide on an implementation and still haven't decided. The churn is utterly useless if you are actually trying to build something. |
I'm not jumping ship for Redux because it's slightly better. I'm switching because it's a significant leap over classical Flux. I do understand everyone's frustration but the flip-side of churn is things marginally improve and then grind to a halt. I'd rather move on to the next great thing. That being said, if someone wants to take over maintaining Flummox I'll happily oblige. |
I took the bait and tried redux for a couple days. Seemed 'functional' for no other reason but to be functional. If a lib is going to be about 'state', I don't want it to shy away from it. I'm trying out https://github.com/omniscientjs/omniscient now. If it lives up to its claims, then thats a significant leap. |
Sorry, this just doesn't compute to me.
You may not be very impressed today, but at its core the way Redux is built allows for very powerful developer features that you won't find in any other Flux library because of their non-functional design. I'll be releasing some of the tools I'm hinting at after my ReactEurope talk. That said, Omniscient is great and I hope you find it better suiting your taste! |
ARGGGGGGHHHHHH!!!!!
The text was updated successfully, but these errors were encountered: