At the end of the day, I want to write the least amount of code, have the best performance, and be able to have an easy way to test my code and all I had to do was get over putting extra code in my DOM and structuring my javascript in a way I wasn't familiar with.<p>Browse the AngularJS source code and you'll see it littered with jsperf, they care about performance and you'll learn a lot about javascript performance.<p>You'll write fewer files in AngularJS since you don't need to create a file for every view and model. I'd say I write 60% less javascript.<p>Testing is easy, AngularJS integrates easily with Testacular, and because you never manipulate the dom directly, all your code you write is logical making writing test code straight forward.<p>You won't see many tutorials but when you google for specific problems you'll find many jsfiddle examples which made learning AngularJS easier than BackboneJs and EmberJS.
I agree with most of this, Ember.js is great. However, I'm not so sure on ember-data. It seems like it has great potential and will eventually turn out to be excellent but currently I've found it to be very frustrating when you actually try and use it.<p>To me ember-data is currently either you use it exactly as we specify and it might work but if you attempt to do anything that even slightly deviates from this then you're pretty much out of luck.<p>Firstly, it has a trivial to challenging barrier of entry depending on your skills/environment; it requires a working ruby environment and the ability to build ember-data from the git repo.<p>Then once you start using ember-data you'll most likely find yourself running in to all sorts of problems that involve you delving into the source code to find out what on earth is going off (no docs). Also I fell in to the trap of assuming that ember-data should do something and trying to figure out what was wrong with my implementation when it turns out it can't actually do that. For example, ember-data does not automatically update hasMany collections when you fetch a model with a corresponding belongsTo. Because of this you have to specify every single id of the related models for your hasMany relationship in the parent model's JSON and good luck trying to hack your way around this by appending models to the hasMany collection yourself.<p>As I said though, it does appear to have promise and to be fair it does not claim to be ready for production. However, I think it is a bit early to be attaching words like "love" to ember-data just yet. Ember.js on the other hand currently seems excellent and when ember-data becomes production ready I think they'll make for a very powerful combo.
... So you love EmberJS because backbone was the only thing you used before and the only thing you have to compare against?<p>I've used both Angular and Ember extensively, and AngularJS trounces on EmberJS in both performance and ease of use.
Other than Ember Data, it seems like all the pieces here are things that marionette has. I was super interested to read this, swinging more towards marionette myself, just to get a perspective on what convinced you to change. But there really wasn't much comparion, it seemed to just be you going over the features of ember.<p>If you don't mind answering here, what made you go so strongly with ember over marionette?
<p><pre><code> - How fast is your app?
- How productive is your team?
- How productive is Ember community?
- How many Ember libraries do exist in Github?
- How many JavaScript libraries exist in NPM?
- How many of the NPM libraries can be used in client-side?
- How robust is to manage Ember dependencies?
- How simple is to manage Ember dependencies?
- How easy is to debug an Ember app?
- Do you set break points ?
- How easy is to hunt memory leaks in an Ember app?
- What package manager do you use?
- What else libraries do you use?
- Does your code integrate with other code written using Streams, EventEmitters etc?
- How would you reuse Ember in your backend code?
- How replaceable is your code?
- How large is your code?
- Is using large frameworks a best practice in JS community?
- Have you seen alternatives like components http://github.com/component ?</code></pre>
Good read, I'm a sucker for those love it/hate it posts.<p>Still being in the process of playing around with Ember and I really want to like it, but my mine gripe is still the documentation.
Take for example the linkTo helper which I wanted to use with the Twitter Bootstrap navigation. I found a few examples on how this could be done, but no API documentation for the helper? The Ember.LinkView documentation does not really help as well.<p>Maybe I'm blind or just too inexperienced with Ember.Js Views, but something like that really puts me off.
I really wanted to like Ember.js, but I had difficulties writing tests for my app and there isn't substantial documentation for it, which was a deal breaker for me.