In reusable components, where did @Binding create long-term pain?

Exposing @Binding in reusable SwiftUI components creates maintenance problems because it locks callers into specific timing assumptions. When behavior needs to change, every caller breaks. The solution is replacing bindings with explicit actions and values, trading a one-time breaking change for long-term flexibility. Bindings act as rigid contracts that prevent API evolution.