,
3 tweets,
2 min read
Read on Twitter
At a dinner with @mweststrate and @getify we were trying to figure out how one-way data flow is fundamentally different from two-way data binding. For example, what's the difference between
A-->B-->A (one way) and A<-->B (two way)?
We found a good answer:
A-->B-->A (one way) and A<-->B (two way)?
We found a good answer:
It turns out it's not one-way vs two-way distinction that matters, what matters is how many "primary" sources of truths there are.
In two-way data binding, there are multiple sources of truth and no authoritative answer. In one-way flow, there is a single source of truth.
In two-way data binding, there are multiple sources of truth and no authoritative answer. In one-way flow, there is a single source of truth.
Fun fact: Apple is now copying the frontend community's practices with SwiftUI, and they use one-way data flow: developer.apple.com/videos/play/ww…
For those of you who have heard me sharing about lenses for state management, the SwiftUI bindings support getter setters too!
For those of you who have heard me sharing about lenses for state management, the SwiftUI bindings support getter setters too!
