[xonecasacenox]

I can understand why you'd think of me as a Angular diehard, but I'm not. I try to choose the best tool for the job, and because of it's structure Angular was the best choice for this project. If Ember or Backbone had been more suited I would just as easily had a love affair with them too!

As for your bad experience, I can see how that can happen with Angular, but I can also see that happening in other ways with other libraries. In my opinion that is solved by using good code patterns and writing code for others, not for yourself. I'll leave this relevant quote:

"Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live." - Martin Golding

[goldfeld]

Angular, Ember and Backbone are all MVCs. They're more or less different shapes and sizes of a hammer. You'd be missing saws, which can cut through all this, ahem, object oriented crap. And don't forget the simple tools, which can be composed any number of ways and don't make everything look like a nail.