title: What's the difference between Ember.computed.alias and an Ember.binding?
body: <p>In Ember, defining a property as a computed alias to another property (or another object's property) using <code>Ember.computed.alias('otherProperty')</code> seems to have basically the same result as defining it as a binding to that property using <code>propertyNameBinding: 'otherProperty'</code>.</p>
  
  <p>I've looked at the source and the documentation but I can't find any reason why one would be preferred over the other. Obviously templates use bindings, which is fine, but for properties in e.g. controllers, or for referencing a controller's property on a view, is there a difference?</p>