@efx wrote:

The guides have a whole page on observers but caveat their use:

Note: Observers are often over-used by new Ember developers. Observers are used heavily within the Ember framework itself, but for most problems Ember app developers face, computed properties are the appropriate solution.

I would like to hear better arguments why application developers should avoid observers. I’m aware of @stefan’s fine talk on the subject but have not watched it. Interestingly, @acorncom mentions linking to the talk for the guides in an archived issue. I look forward to the shimmering land of Octane-happiness but prefer examples for today’s applications.

reasons why not

1. creates an ambiguous data flow contrary to the DDAU (Data Down Actions Up)
2. often leads to using setters or imperatively maintained state when most uses just need to derive values ( à la decorators)

Hopefully this post can spark constructive conversation for making the guides more robust.

Posts: 1

Participants: 1

Read full topic