Introducing: Ember Objects
Most objects in Ember, including Routes, Models, Services, Mixins, Controllers, and Components extend the
Why Ember Objects?
The most important reason is that an Ember Object can be watched for changes – or observed. For example, being observable is important for computed properties. It is one of the fundamental ways that models, controllers and views communicate with each other in an Ember application.
More on Ember Objects
The @ember/object package also provides a class system, supporting features like mixins and constructor methods, and being observable.
Array prototype with its @ember/enumerable interface to provide change observation for arrays.
Finally, Ember extends the
String prototype with a few formatting and localization methods.