Nope. Lack of two-way binding is a blessing. It makes everything predictable. >It seems going back to the method of handling data updates through onchange even

Nope. Lack of two-way binding is a blessing. It makes everything predictable. >It seems going back to the method of handling data updates through onchange events in a manual fashion would be a colossal step backwards from say, knockoutjs. It's not exactly "manual fashion" because React updates everything according to `state` for you. If you have many interdependent fields, make them update `state` correctly, and React will keep them in sync with it. In fact I find it easier to make complex input logic with one-way bindings because the data always flows one way. It's a tad more code to write, but you see exactly where your updates are happening and what's causing them. Two-way binding tends to get very complicated as soon as you need more complex logic. One-way binding doesn't have this problem.