[lumpypua]

shrug They address different problems. Reactive systems are great but they aren't an overall architectural approach. You have to come up with that yourself.

Flux is an architecture.

I used BaconJS and I found that my overall page event and data flow ended up being reactive spaghetti. Architecture is not my strong suit. One of the great things about flux is having extremely strong conventions about where everything goes:

- All interactions are through actions.

- All state is in stores.

- No mutable state in the actual UI.

- etc.

What's your overall dataflow architecture look like using RxJS or BaconJS?

[mjohn]

There is nothing stopping you using a flux-like architecture with RxJS or BaconJS. For example, instead of action creators you can push to a Bacon.Bus that is listened to by your store, which can be a Bacon.Property.

I found using BaconJS much nicer if I needed to transform data from asynchronous requests because you end up with a much more functional approach.