> just using dataflow programming directly is both simpler and faster,
But a good reactive system is simpler to write, understand, and debug. At least that is what I found in my latest project.
But a good reactive system is simpler to write, understand, and debug. At least that is what I found in my latest project.
Because what you write certainly sounds a lot like just dataflow.
To me, dataflow is simply a stream of data triggering calculations even if the data is unchanged. e.g. the stream of 1,2,2,3 would cause four calculations.
Reactive means that only 1,2,3 would appear to the calculations. In other word only changes are reacted to.
My framework is reactive by these definitions.