Which Flux implementation should I use?

[koistya]

Relay by Facebook + examples

redux by Dan Abramov

flux by Facebook + examples

alt by Josh Perez + examples

reflux by Mikael Brassman + examples

flummox (deprecated) by Andrew Clark

fluxible by Yahoo

fluxxor by Brandon Tilley + examples

marty.js by James Hollingworth + examples

fynx by Alan Plum

McFly by Ken Wheeler + example

DeLorean.js by Fatih Kadir Akın + examples

fluxify by Javier Márquez

Comparison: https://github.com/voronianski/flux-comparison

[buxel]

This is closed but i still like reflux for its simplicity

[koistya]

@ChaosD It seems like Reflux misses some important characteristics of the Flux architecture: Can you dispatch actions in a predefined order with Reflux? Make sure that all the actions are dispatched synchronously (the next action dispatching does not start before finishing dispatching of a previous one)? Can a single action creator / method dispatch more than one action at a time (a couple of different actions)?

[buxel]

Be warned, I most certainly cannot answer your questions in a satisfying way because I'am just getting started with react.
I like the simplicity because it seems to streamline the whole process a bit more (maybe too much for you) and makes it easier for me to get started with. What i got so far is, that its possible to order your "dispatching", quoting the readme here:

waitFor is replaced in favor to handle serial and parallel data flows:

• Aggregate data stores (mentioned above) may listen to other stores in serial
• Joins for joining listeners in parallel

I could not find anything about action creators dispatching multiple actions but since actions dispatch themselves, i imagine you could simply call multiple actions to get what you need. I'am not quite sure if I got you right here but i cannot imagine a situation where this might be required. Could you elaborate?

These articles seem to address some of your concerns and helped me a lot understanding reflux:

• http://blog.krawaller.se/posts/react-js-architecture-flux-vs-reflux/ (basic info)
• http://spoike.ghost.io/deconstructing-reactjss-flux/ (probably your answers)

[buxel]

Have you reopened this issue for further discussion or are you already considering reflux? I'd love to hear your opinion about it because I'am also about to make this decision.

[buxel]

I just studied the flux docs again and it seems that you are right. if you want to stick to flux as close as possible, reflux might not be the best bet. Fluxxor is new to me, thanks for pointing me there. I will definitely check it out.

[buxel]

I played a bit with Fluxxor and it convinced me. It is really better if you do not want to be led astray from the Flux pattern.
What do you think about McFly?

Maybe it is time to rename the issue... ;)

[f]

Try https://github.com/deloreanjs/delorean which we build and it's too
simple.
7 Kas 2014 09:05 tarihinde "ChaosD" notifications@github.com yazdı:

I played a bit with Fluxxor and it convinced me. It is really better if
you do not want to be led astray from the Flux pattern.
Have you seen McFly? http://kenwheeler.github.io/mcfly/

—
Reply to this email directly or view it on GitHub
#22 (comment)
.

[buxel]

@f , in what way Delorean is different to the previously mentioned? How does it handle the concerns @koistya mentioned with reflux?

Btw, I really love how so many Back To The Future themed libs pop up so fast! :D

[buxel]

A nice summary can be found here:
https://reactjsnews.com/the-state-of-flux/

[patrick-fls]

I personally settled for Fluxxor. I think it's the perfect blend between vanilla flux and reduced boilerplate and you can further reduce it with custom mixins. If the project ever dies, it would be easy to migrate. It's a non negligible advantage if you're in react for the long term.