I've been treating Ember-Data very cautiously, and feeding it carefully prepared data. The biggest irritations involve multi-record commits and validation/error

I've been treating Ember-Data very cautiously, and feeding it carefully prepared data. The biggest irritations involve multi-record commits and validation/error handling. But it's working well enough for my straightforward needs. Still, don't touch it unless you like reading the source, and you're willing to use something that's marked "NOT PRODUCTION READY". The Ember.js tutorial situation is abominable, but I see two or three new tutorials are out in the last two weeks. And after much head-scratching, I finally figured out what's up with Routes vs. Controllers vs. Views. Keeping all those caveats very firmly in mind, I'm really happy to be using Ember. My code is lot cleaner than that of my previous web apps, and features are getting done fast. When it hits 1.0 (including Ember-Data!), I think it's going to be one of several excellent choices.