> Yes, but that's pushing the responsibility to...

# android

[vmironov]

Yes, but that's pushing the responsibility to the passer of the config, which we talked about before.

@eski: you have the same responsibilities when you use any DI framework. DI container itself needs to be configurated and I don't see how it differs from providing a different config.