I'm very glad to see that this answer hasn't been closed as not constructive! It seems like most popular questions like this are, even though they're incredibly useful and insightful.
I was leaning toward learning Ember, but this post makes me really curious about Angular. In particular, the ease of testing has my interest piqued. Is testing as simple/easy with Ember? I know that unlike Angular, Ember doesn't have DI as a core feature. Either way, I should probably just flip a coin and start learning!
I was disappointed that it hadn't been closed. The first answer is a backhanded dig at non-angular developers saying that angular is about architecture and implying that the others aren't.
I like angular but "angular architect" rolls off the tongue too easily.
You're disappointed that a really informative answer has not been closed because of some subtext you've read into it that may or may not actually be there? That doesn't seem like a very productive attitude to me.
Actually, no, the person who wrote the so-called "answer" which is more like an essay (and therefore not a proper Stack Overflow response) isn't a google employee. I didn't mean to imply that.
OK, then I'm unclear on why you brought up my employer. Did it have something to do with my support of the answer in your mind? Like is Angular a Google project? Or was it just some random thing you could attack?
How is the framework having unit tests ( and please, don't say TDD, when you mean unit tests) say anything about how testable code written using the framework is?
I was leaning toward learning Ember, but this post makes me really curious about Angular. In particular, the ease of testing has my interest piqued. Is testing as simple/easy with Ember? I know that unlike Angular, Ember doesn't have DI as a core feature. Either way, I should probably just flip a coin and start learning!