Angular is vastly superior to Ember technology wise; Their approach is also more future proof (No stupid getter/setter, string templates, the architecture is based on something very close to web components, etc)
Thank you for your well-reasoned comment. However, it sounds like you're basing your opinion on some misinformation. That's okay, it happens to everybody. :)
Ember.js is extremely future-proof. Yehuda Katz, who I work with on Ember.js, is on both the W3C and TC39, the committee designing the next version of JavaScript. Needless to say, we have a pretty good idea of what's planned for the future of the web platform; we're also very involved with the standards bodies to make sure it is as powerful as possible for building web applications.
Setters and getters are a trade-off. While we'd prefer not to require them, the alternative is that you have to diff objects every time a change happened. And not just a change, but a possible change—which means in response to almost any event. By using getters and setters, we avoid this particular performance footgun.
Actually, Ember views have much more in semantically common with Web Components than Angular directives, despite the fact that many people like to repeat this misinformation. For more, see this thread on Google Groups: https://groups.google.com/forum/#!msg/polymer-dev/4RSYaKmbtE...
Yes, forgive my tone. I should just have said that when it comes to picking a third party framework (I don't always do), I personally prefer the compromises made by Angular than the ones made by Ember. Of course, the biggest compromise of Angular (dirty checking all over the place just to be sure) also make it unsuitable in a number of situations :)
About future-proof, I mean the Angular programming model is closer to what we'll be doing in a few years (There won't be any get/set or computed properties anymore); I never implied the Ember team is not aware of what's coming.
To me none of the frameworks are ideal, although I find Ember or Angular well architectured, as far as implementing the vision of the authors go. With the current capacities of Js and no compilation steps, compromises can not be avoided :-(
Ember.js is extremely future-proof. Yehuda Katz, who I work with on Ember.js, is on both the W3C and TC39, the committee designing the next version of JavaScript. Needless to say, we have a pretty good idea of what's planned for the future of the web platform; we're also very involved with the standards bodies to make sure it is as powerful as possible for building web applications.
Setters and getters are a trade-off. While we'd prefer not to require them, the alternative is that you have to diff objects every time a change happened. And not just a change, but a possible change—which means in response to almost any event. By using getters and setters, we avoid this particular performance footgun.
Actually, Ember views have much more in semantically common with Web Components than Angular directives, despite the fact that many people like to repeat this misinformation. For more, see this thread on Google Groups: https://groups.google.com/forum/#!msg/polymer-dev/4RSYaKmbtE...