What I also like is that the constructor is the only part of my classes that knows about the component
Yes, but it is still a dependency. Make this technique widespread in the codebase and you’re on the verge of “service locator”.
At the very least, this was an interesting read.
I recently demonstrated how to implement dependency injection in Android without any frameworks at all, and then showed how Dagger fits into this picture.
This post does basically the opposite — takes a specific way to structure Dagger code in the app…
Great overview, really!
So it started — DDD in Android. I predicted that it will happen in 1–2 years, but looks like it might pull in a bit.
This post is really great because it summarizes the real spirit of DDD as Eric Evans tried to convey in his book.