... sure, it depends. But there are even more reasons than over-propagation of change events to avoid strict two-way model/view binding.

One of them is that the data often isn't the same. The view displays a computed value from the model, and the model should receive the "real" value upon a change. For example:

    <span data-value="<%= feed.get('kind') %>">
      <%= feed.entitle() %>
    </span>

    ... becomes ...

    <span data-value="article">
      NYT Article
    </span>

When the DOM element is chosen, the model's value should be "article", not "NYT Article" ... and perhaps the change should happen immediately, and perhaps the change should happen only after a "Save" button is clicked.

With concrete two-way binding, you may spend more time configuring all of your DOM elements, and configuring when your models should be considered "changed", and when they shouldn't -- than you gain by tying them together in the first place.