I was just having a conversation with a friend of mine regarding if we should spend more effort in learning Angular. While I can understand making breaking cha

I was just having a conversation with a friend of mine regarding if we should spend more effort in learning Angular. While I can understand making breaking changes, and sometimes very big ones, I feel like this timing is incredibly poor, and is coming when many people are just learning the framework. At this point in time I do not want to invest any more time in the framework or its changes: the stable version I use will soon be obsolete; I can't learn the "new" version or use the "new" version now; and I don't know when the point will come when the AngularJS core team - and Google - are happy with the decisions they have made, if the point EVER comes ( especially re: Google ). I also feel that while they addressed many of the concerns that the community had, the decisions they made were not strictly speaking "necessary". For example, removing all the ng-* stuff "looks" nicer, but it is now less clear which code is repsonsible for handling that declarative behavior. I would have preferred a mechanism which allows you to specify other "included" directives in a directive definition in a clear and concise manner ( without hacking on compile or link functions ). I think I'm going to try Ember or something else. I liked Angular for what it showed me - that a data binding approach could really ease the pain of radical design changes, for example - but I'm not going to be sticking with it after this project. Time to move on.