jvm-redux positioning vs rxjava

[beyondeye]

Something that need to be discussed is positioning of jvm-redux vs rxjava. Even for the Javascript version this is an issue (see for example here the end section "Why Redux? Why not RxJS 5?". This is even more of an issue on Android.
Basically the question to answer is: what is the added value of redux vs rx, for java programmers?

[glung]

Thank you @beyondeye for bringing that up, wether it is yes or no, I agree we should have a clear answer to that question.

For me the answer is simple : Rx is not required, hence should not be added to keep the API minimal. An extendable API to add reactive streams is nice to have. - I guess this is aligned the article your linked.

In other terms, I think the API should be implementable by other stores with minimal frictions. Some stores don't use RX.

Note : this project is not Android specific.

[beyondeye]

My question is not about the api at all. It is about why people should use redux instead of rxJava. They are both based on reactive functional programming ideas. But rxJava is much more powerful. The question is why the heck people should bother learning redux if they can do all what they want with rxJava,which is already extremely popular on the Jvm

[beyondeye]

If you want you can rename the issue "how to market jvm-redux to developers"

[glung]

I understand. I guess it the very difference between https://cycle.js.org/ and redux.
If you ask me, I think both are valid unidirectional data flow architecture.

[beyondeye]

Here a couple of links for reference

• a discussion on SO on the issue: Redux & RxJS, any similarities
• a discussion of redux vs ciclejs (a bit outdated: almost two years ago, but still useful)
  André Staltz - Some problems with React/Redux
• a lot of links to discussions react-redux-links/pros-cons-discussion