if it works for you <@U0NT624JZ> :thumbsup: but da...

# kodein

[ian.shaun.thomas]

if it works for you @rocketraman 👍 but daggers generally useless errors are why I'm done using it. I would rather type more code or do anything else if it means getting useful errors. The other major smell is almost every project I have seen in the real world using dagger is using it wrong. They almost always have a god class for the injections (all definitions in one module) and in multiple places they have some work around because they couldn't figure out how to get dagger to do what they needed. Not saying dagger is bad just that I have seen the same issues from multiple teams of devs so that seems like a pattern to me that the library isn't very good.

[rocketraman]

Thanks for your reply. We use dagger properly -- no god class and many modules contributing functionality, like configuration, database, json services, boot module to handle startup/shutdown, etc. IMO, this has less to do with the injection framework and more to do with basic design and architecture hygiene. However, agreed that many people don't understand the Module concept. Shouldn't this also be an issue with teams using Kodein, since it support modules as well? If not, why not?

How do you find the startup performance of Kodein vs Dagger?