Skip to content
This repository has been archived by the owner on Jul 13, 2020. It is now read-only.

How does this library compare to Dagger 2? #34

Closed
netimen opened this issue Mar 23, 2016 · 1 comment
Closed

How does this library compare to Dagger 2? #34

netimen opened this issue Mar 23, 2016 · 1 comment

Comments

@netimen
Copy link

netimen commented Mar 23, 2016

What are the main pros and cons of this library over Dagger 2? Why should one choose injekt? It would be great to add a short section to README describing this

@apatrida
Copy link
Contributor

Read the documentation for Dagger 2, then read the documentation for Injekt. If one makes more sense to you than the other, use it. Injekt is a object registry pattern where you are in complete control, and using default values for constructors that call Injekt, or initializing properties with Injekt or delegates of Injekt, you can easily build anything another dependency injection system can do but without anything being hidden. And it will also work in unit tests without even having to use injection if you layer things correctly. Again, because you are in complete control and everything is obvious. I don't use Dagger 2, never have, and didn't like the type of library it was when I read the docs so I moved on to my own.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants