[ethermal]

I'm throwing my 2 cents in, although I haven't built a large scale app with either, I did do a full evaluation of both before my latest large app and I decided on neither one. There were many reasons but every time I wanted to do anything that was remotely non-trivial both fell apart. Although most of that had to do with the MVC pattern more than the actual framework (but the two are tied intricately) In the process of evaluating these two frameworks I found KnockoutJS and I chose it for my large project that is one year into development. After one year with it I love it more now then when I first started. It's not perfect but it is a really well thought out framework, it does lack some documentation, ko.utils I'm looking at you. But it's documentation is vastly superior to the other two frameworks, at least it was a year ago. It's very stable and I prefer the team's approach. The two binding and subscription model is great for solving some intricate problems. It's easily extensible with custom bindings and unlike angular doesn't favour bad coding habits that lock you in to the framework, I forget the name now but their custom HTML tags (I think they call them directives) is nothing but bad news and vendor lock in.

[TylerE]

That's pretty much the same conclusion I came to. Wake me up once ember-data is stable and can support things like range queries and pagination, and just generally dealing with a small subset of data.

[steveklabnik]

http://eviltrout.com/2013/03/23/ember-without-data.html