Wait, hang on. Say that you're building a app that has lots of business logic and interrelated data. For that sort of app, history shows us that a rich object model can often be the best place to put your logic and data relationships - from both a testing and ease-of-development perspective. That's the approach that frameworks like Ember advocate - but Ember forces you to extend on its own object model.
- Lazy-loading data relationships between models
- Decorating loaded data with business logic
- Object identity uniqueness (critical for bindings to work as expected)
- Computed properties for models
Attendees will leave with an understanding of how a rich object model can help them build beautiful, fast and easy-to-maintain apps.