Hacker News Reader

Both frameworks have their strength and weaknesses. I think Ember is a heavier and more verbose,but it's easy to integrate third party widgets without having to rewrite them. While I was coding something to learn AngularJS https://github.com/Mparaiso/markme-silex , I spent most of my time fixing race conditions between the digest cycle and the third party widgets , and sometimes it was reaslly hard to figure out why the model wasnt updating,or why the view was when the model didnt change in appearance. ( I had to integrate masonry,bootstrap modal,tags.input,autocomplete and a few others).

But again,since AngularJS takes care of everything else,that's a tradeoff.Angular solves the architecture problem with dependency injection.

Thanks josh, just in case you want to stick to the Backbone that, there is a tutorial for that ;) http://blog.stamplay.com/how-to-build-an-about-me-clone-with...

Just curious - what influenced your decision to roll with Ember instead of Angular, and what particularly makes you doubt your decision - i.e. what did you find more appealing in this article about Angular?