Ember really strongly pushes you to use Ember only for pure Ember web applications. Though there are a few of us that like to nest Ember just for a single component on a webpage. While it can be debated that Backbone or Angular is better suited to this situation I personally still really like to use Ember.
So you want to pass or ajax your Ember.Objects or Models to a JSON service. While it is possible, you might get some unexpected behavior and ill explain these to you, as well as the solutions I’m currently using.
In previous versions of Ember the Ember.Object.create and Ember.Object.extend would behave very similar. You could pass in your overrides/mixins and methods that call _super. However supporting this is very expensive and usually an unnecessary overhead. During normal run-time we need very few extends, actually mostly only during set up, but we do lots of creates which must incur the penalty of supporting these unnecessary features. Read More
I’ve come across a few instances where I’ve seen people try to convert integers into a negative value. Read More
Unfortunately jQuery selectors aren’t stupid proof. Its all too easy to chuck a long string of junk into your selector and not have a single problem. You might have the attitude of, “meh it works” and not give it any more thought of if there is a better way.