[<<][softarch][>>][..]
Thu Feb 14 22:07:56 EST 2019

redo, push_change,

really turns things upside-down, back to simple imperative
programming.

imperative isn't bad, as long as it is:
- idempotent
- possibly skipped on no-change

i.e. as long as it's inside some kind of dependency framework.

then the whole thing is still "pure" or "reactive".



[Reply][About]
[<<][softarch][>>][..]