Comments on: EmberJS: Initial Impressions (Compared To Backbone)

By: slowhands

slowhands — Mon, 13 May 2013 02:41:00 +0000

I agree with this post 100%. The takeaway for me is that EmberJS gives us lots of help keeping things together, sort of like a puzzle that pieces itself together. The conventions are nice and all, but there’s a rebel inside of me. Even though the instructions in the box are for building a car, I’m building a space ship.

By: Dave Romero

Dave Romero — Wed, 19 Dec 2012 16:25:00 +0000

Derick, I have to say thanks for writing this fantastic piece. It’s rare to come across an author who remains so objective in comparison. Bravo!

By: jzinedine

jzinedine — Mon, 29 Oct 2012 20:05:00 +0000

Than,s for write up and glad to see it updated as we go forward

By: Ian Lovett

Ian Lovett — Thu, 11 Oct 2012 20:46:00 +0000

I am having difficulty deciding between Backbone & Ember. Thanks for this write up. I am thinking that even though the Ember library is larger, eventually, if your project is big enough, the boilerplate code created with Backbone will get grow at a faster rate
whereas Ember will grow at a slower rate…

Documentation is also a huge factor… but this can only get better for Ember as it gains momentum… this was written 8 months ago, it would be interesting to see how much more documentation there is now than there was back then.

Thankfully both of these are modular and play well with RequireJS… a prime factor which has me deciding between these two.

By: Anonymous

Anonymous — Thu, 12 Jul 2012 22:02:00 +0000

At Blurb, we’re using Ember to run one of our online book editing applications. We do rely on AJAX calls to save the data. With the exception of supporting IE’s XDomainRequest object (*grumble*), it hasn’t been painful to integrate. If you’re interested in poking at a real world Ember app, make a Facebook book on Blurb and after you’ve made the book, you’ll get to a page with “Enhance for iPad.” That link will take you to the full editor. [ http://www.blurb.com/apps/facebook ]

Our ebook preview is also driven by Ember, but is far less complicated than the editor. [ http://www.blurb.com/ebooks/reader.html?e=288422 ]

By: Derick Bailey

Derick Bailey — Mon, 04 Jun 2012 19:20:00 +0000

i’ve stuck with underscore templates for now, only because it doesn’t require any changes in the way i build apps. i still want to try handlebars, and i know a lot of people that are using it with backbone. but i haven’t had a chance yet

By: Volkan

Volkan — Mon, 04 Jun 2012 18:46:00 +0000

Have you had any change of opinion about Handlebar? I’m thinking of following your lead and switching over form Mustache?

By: Jo Liss

Jo Liss — Wed, 02 May 2012 13:12:00 +0000

> Re documentation, I found myself browsing around the Ember source quite a bit. The tutorial on emberjs.com only goes so far I guess.

Just an update on this, there is now also the docs.emberjs.com reference site, extracted from the inline code documentation. It’s seen a lot of documentation love in the last few weeks, and I find it quite usable.

By: Jo Liss

Jo Liss — Wed, 02 May 2012 13:09:00 +0000

I’m using Ember-data, talking to active_model_serializers on the server side, and it’s working well so far. I don’t think trying to roll your ad-hoc synchronization code (with jQuery.ajax and friends) is sustainable.

By: Anonymous

Anonymous — Wed, 02 May 2012 11:26:00 +0000

I realise that might sound a little bit like “Mwahhhh, Mwahhh, I’m annoyed that this totally free thing doesn’t do *exactly* what I want”.

Just curious as to how anyone would use Ember in the real world.