> That is so weird. The reason why we have DI and DI frameworks is because we are asked in requirements to make things configurable out-of-code (and at runtime)

> That is so weird. The reason why we have DI and DI frameworks is because we are asked in requirements to make things configurable out-of-code (and at runtime), because someone wants to use a pretty UI or a config file of sorts to set up which behaviour is used to do $thing. Which is ironic in regard of DI frameworks that rely on in-code annotations to wire dependencies, especially in compiled languages. Let's not even get started with languages that do not allow ad-hoc object/value creation from external manifests directly, like Go.