[throw_m239339]

It's a solution looking for a problem. The reasoning behind IoC containers was the ability to deploy binaries and at the same time be able to simply configure them with manifests without having to recompile the binaries or rerun unit tests.

There is absolutely no reason to use an IoC container with a dynamic language. None, even when one is using Typescript.

This is an "ideological" framework where the "ideology" is forced at all cost, surprising since Angular creator was a Java consultant for Adobe and then Google.

Changing a little script takes zero effort.

[mgechev]

A common pattern is to separate the instantiation of an abstraction from the place you're using it. There are variety of ways to implement this in different technologies/frameworks.

The way Angular implements it is the way our team believes is the most scalable and expressive way. It has been tested in over 2k projects inside of Google and hundreds of thousands of external apps and seems to be working well.

At the same time, this is just a feature that the framework provides. Just like any other technology, you can pick what pieces of the entire system which works for you and ignore the rest. That's not part of the beginners journey and shouldn't be, especially for folks unfamiliar with the pros and cons of this approach.