i was uncomfortable with the fact that it was being done in core, and I know from personal experience that it will only take a good enough reason to do somethin

i was uncomfortable with the fact that it was being done in core, and I know from personal experience that it will only take a good enough reason to do something even dodgier with that type of thing. my recommendation was that they remove it from core, and have it be opt-in through the use of ngmin. they are actually removing it completely from angular 2.0, so it's a moot point really. http://daemon.co.za/2014/03/complexity-creeps-concerned-for-future-of-angular http://daemon.co.za/2014/03/complexity-creeps-concerned-for-... I also stated that I was fine with the dirty checking, because it worked better than it had any real right to. And best of all, it's only 'for now' http://daemon.co.za/2014/03/why-wrong-to-be-afraid-angular http://daemon.co.za/2014/03/why-wrong-to-be-afraid-angular