I came to the insight, that the Flux/Redux Pattern is "better than" MVVM.
The main point is a better understanding/debugging of the flow of events.
In MVVM we have typically databinding, sometimes bidirectional, sometimes on different threads. At runtime the events in the application are like a gunfight with bullets flying from/to all kinds of directions.
In Flux/Redux, we have in contrast the unidirectional dataflow, which makes it easy to understand/debug the system. This is more like a shooting range. The bullets fly from A to B.
In my day job I switched over from MVVM to Redux and think it "is better". Unfortunately I didn't have time to share some code.
I came to the insight, that the Flux/Redux Pattern is "better than" MVVM.
The main point is a better understanding/debugging of the flow of events.
In MVVM we have typically databinding, sometimes bidirectional, sometimes on different threads. At runtime the events in the application are like a gunfight with bullets flying from/to all kinds of directions.
In Flux/Redux, we have in contrast the unidirectional dataflow, which makes it easy to understand/debug the system. This is more like a shooting range. The bullets fly from A to B.
In my day job I switched over from MVVM to Redux and think it "is better". Unfortunately I didn't have time to share some code.