|
You are here |
dagger.dev | ||
| | | | |
ryanharter.com
|
|
| | | | | I recently gave a presentation about how Dagger works under the hood, and I was once again struck by the elegance of the javax.inject.Provider interface. The interface is so simple it almost seems useless, but it's also incredibly flexible, and forms the basis of much of the code generated by Dagger. Like many dependency injection frameworks for JVM languages, Dagger uses and builds on the standard set of annotations for injectable classes defined in JSR-330 and provided in the javax. | |
| | | | |
msfjarvis.dev
|
|
| | | | | Dagger is universally intimidating to beginners and I want to change it. | |
| | | | |
daniel-siepmann.de
|
|
| | | | | Explanation of how Dependency Injection works for TYPO3 Extbase (prior TYPO3 CMS v10). | |
| | | | |
blog.theamazingrando.com
|
|
| | | The point of this post isn't to convince you of the usefulness of Dependency Injection there's been plenty of pixels spilled about it already. Instead, I want to talk about using Dry::Container to alleviate some of the pain points that DI introduces. | ||