Animation APIs parameterized by eg duration and curve are fundamentally opposed to continuous, fluid interactivity.
Conversation
declarative solution: Scene render as a reduce() on stream of entire history of signals observed including timers/touches.
2
6
Yes! This is essentially Elm's approach, right?
1
1
I should look at Elm. , and I were talking about how React's current API can be a special case of it.
3
2
The thing about reduce is that it's like epicycles. It can model almost anything—so yields less structure
1
2
I think the *spirit* of reduce is that you're always returning the next state, instead of mutating. That's what I'm after.
1
If a "component" has specific methods (more structure) that return next states instead of a reduce func, satisfies the same.
1
Replying to
Yeah, a function which returns next state isn't exactly reduce because it can't alter structure (eg add more intermediate states)