I have a property which is based on time and I have properties which depend on that property. The problem is that the whole tree gets recomputed every time the time property changes. In order to get around that problem I have introduced observers:
Is that the right way of accomplishing this? Further, why is it that Ember itself doesnt halt the computed chain if it notices that the computed value is === the cacheValue. Yes, two identical objects will still incur a recompute, but that should be a fast way of shortcutting a lot of recompute logic, right?