butterknife VS Dagger2

Oof, Infinity uses the long deprecated butterknife, and I'm unable to compile on my m1. Fave part of programming: getting things to run the first time.

As said in the title, we will focus on the dependency inversion principle and one of its application : dependency injection. For production-ready applications, it would be better to rely on a framework and not implement its own container. For it, the java ecosystem have 3 frameworks available : Spring, Guice and Dagger.

At Reddit, we use Dagger 2 for handling dependency injection (DI) in our Android application. As we’ve scaled the application over the years, we’ve accrued a bit of technical debt in how we have approached this problem.

Confusing. I initially thought someone ported the Dagger DI framework to Python: https://dagger.dev/

I'm currently using Dagger and Anvil for my DI needs. It's been working really well, especially around what Anvil permits in terms of multibindings defined on the type declaration rather than in a module. For example:

Great job, I have been waiting for this feature/fix for a long time https://github.com/google/dagger/issues/2328

Dagger

Of course, but given that there is already https://dagger.dev/ I wonder how much of this "dirk" is derivative, and how is it better than what is already out there?

Are you trying to reinvent, or perhaps improve upon, Dagger?

i don't really consider runtime a requirement of DI, perhaps stuff like spring made that something people are used to. another example https://dagger.dev/