I only reviewed it quickly, but I think they should be using the "then" pattern of promises when saving and transitioning.<p>So this:<p>this.get('model').save();<p>this.transitionToRoute('users');<p>Should be:<p>var controller = this;<p>this.get('model').save().then(function(model) {<p><pre><code> controller.transitionToRoute('users');
</code></pre>
}).fail(function(error) {<p><pre><code> //Feedback for the user
</code></pre>
});
I'm really loving the new Promises/A+ support in Ember—lots of weird corner cases just got a lot cleaner, and it's much easier to bypass Ember-Data when the need arises. See this section of the original post for an example:<p><a href="http://coding.smashingmagazine.com/2013/11/07/an-in-depth-introduction-to-ember-js/#what_about_not_using_emberdata" rel="nofollow">http://coding.smashingmagazine.com/2013/11/07/an-in-depth-in...</a><p>The first rule of Ember.js happiness is "Don't fight with Ember Data." When Ember Data does what you want, it's amazing. When you want to do something that it doesn't support, just fall back to jQuery and promises at the model layer, as shown above.
Really good site. I've also found Ember Sherpa to be very useful once you're up and running: <a href="http://embersherpa.com/" rel="nofollow">http://embersherpa.com/</a>
I'm doing my latest project in Ember... it's cool, but even with a whole bunch of javascript experience, it's been a steep learning curve. I'm starting to get it and I like what I see, but I'd definitely welcome any resources people have in terms of getting to know it in a deeper way.
I've always been meaning to take a look at Ember. When I first started seeing discussions about it about 2 years ago, there weren't many guides or quick examples on how it is different than other frameworks out there. What would the use case be for Ember.js vs something like AngularJS?