Please consider deprecating inferred dependencies

[AdrianRossouw]

Hey There.

I've been working through what was troubling me about angular as a platform,
and I think I finally got it down to the fact that I think that the black magic around
inferred dependencies are going to cause a significant problem for the future
maintainability.

I'm not really angular's model user, because I understand that there's almost never going to be a situation where it's the right tool for what I am doing.

I was however one of the major core contributors for Drupal for many years, and although I'm no longer involved I have been able to see the effects that design decisions in major API's I have built have when used by thousands of developer over almost a decade.

That's not an appeal to authority, just letting you know from what perspective I am looking at this at. I think this is going to be a really big problem 5-10 years from now if you don't take a stand now.

I also think there is a way to keep everyone happy. It's all detailed in my blog.

http://daemon.co.za/2014/03/complexity-creeps-concerned-for-future-of-angular/

[btford]

FYI this "problem" will not exist in ng 2.0. You can look at our new DI system on GitHub: https://github.com/angular/di.js

We (the angular team) agree that the DI annotations are added complexity.

If you have some specific changes in mind for the documentation, feel free to submit PRs to address them. Thanks!