Why I love Ember.js

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.

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.

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.

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.

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.

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.

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.

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.

I've used both Angular and Ember extensively, and AngularJS trounces on EmberJS in both performance and ease of use.

If you don't mind answering here, what made you go so strongly with ember over marionette?

  - 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 ?

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.

Maybe I'm blind or just too inexperienced with Ember.Js Views, but something like that really puts me off.