I care. This is a search field. I don't want the search running after every keystroke. Of course it's bound to a property. How else would you do it?
If you are binding to expensive setters, your design is wrong. In your example,
it is perfectly fine to update a string property 50 times, but if that is also
triggering 50 database updates, then thats an improper design
This is exactly what I'm trying to avoid. That's why I don't want the setter to execute until the user presses enter. That's a pretty normal requirement.